delete_address

Swiggy (Instamart/Food): Delete a saved delivery address for the authenticated user.

📍 WORKFLOW:

  1. First call get_addresses to show the user their saved addresses
  2. Ask the user which address they want to delete
  3. Get the addressId from the user's selection
  4. Call this tool with the addressId

⚠️ WARNING: This action is permanent and cannot be undone. Always confirm with the user before deleting.

See delete_address in actionComing soon

Example

const result = await client.callTool({
  name: "delete_address",
  arguments: {
    addressId: "addr_01HXYZ",
  },
});

Parameters

ParameterTypeRequiredDescription
addressIdstringyesThe ID of the address to delete (from get_addresses response)

Session credentials (user identity, access token) are supplied automatically by the authenticated MCP session - you do not pass them in the tool call. See Authenticate.

Response

Read the tool's data from the result's structuredContent; it follows the Output schema below. content holds a human-readable summary for a model to relay, so don't parse it as JSON. If structuredContent is missing or empty, which can happen on Dineout and Scenes, check isError first: on an error, the first content block can be a plain message rather than JSON. Otherwise it is the JSON envelope below; read data from it, along with any fields next to data (some tools return their payload there, such as booking). See Read tool results.

Where a response carries the JSON envelope as text, it has this shape:

{
  "success": true,
  "data": { /* tool-specific payload */ },
  "message": "optional human-readable message"
}

On failure (isError: true on the result, or "success": false with an error object in the envelope):

{
  "success": false,
  "error": { "message": "description of what went wrong" }
}

See Error codes for the full catalogue.

Output schema

data: {
  statusCode: number;
  statusMessage: string;
}

This schema documents the structured payload returned by delete_address. Optional fields can vary by user state, cart state, and live Swiggy availability.

Schema notes

  • statusCode / statusMessage: service state fields. Prefer accompanying messages/terminal flags and refresh status before taking irreversible actions.
  • Fields marked optional may be omitted depending on user state, cart/order state, and live Swiggy availability.
  • Use returned identifiers and enum values exactly as provided; do not invent fallback IDs, status values, payment methods, or timestamps.

Details

FieldValue
Namedelete_address
MCP ServerSwiggy Food
EndpointPOST mcp.swiggy.com/food
StageDiscover
Behaviourmutating

Next in this journey →

Continue with get_addresses.