delete_address
Swiggy (Instamart/Food): Delete a saved delivery address for the authenticated user.
📍 WORKFLOW:
- First call get_addresses to show the user their saved addresses
- Ask the user which address they want to delete
- Get the addressId from the user's selection
- 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
| Parameter | Type | Required | Description |
|---|---|---|---|
addressId | string | yes | The 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
All Swiggy MCP tools return:
{
"success": true,
"data": { /* tool-specific payload */ },
"message": "optional human-readable message"
}
On failure:
{
"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
| Field | Value |
|---|---|
| Name | delete_address |
| MCP Server | Instamart |
| Endpoint | POST mcp.swiggy.com/im |
| Stage | Discover |
| Behaviour | mutating |
Next in this journey →
Continue with get_addresses.
