get_saved_locations

Swiggy Dineout: Get user's saved addresses for restaurant search. Returns address IDs that can be passed to search_restaurants_dineout.

Swiggy Dineout: Get user's saved addresses for restaurant search. Returns address IDs that can be passed to search_restaurants_dineout.

See get_saved_locations in actionComing soon

Example

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

Parameters

ParameterTypeRequiredDescription

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.

Details

FieldValue
Nameget_saved_locations
MCP ServerDineout
EndpointPOST mcp.swiggy.com/dineout
StageFind
Behaviourread-only

Agent guidance

How Swiggy agents and orchestration logic use this tool. Surface these expectations in your prompts or tool-selection policies.

WHEN TO USE THIS TOOL:

  • User says "near my home"
  • User says "near my office"
  • User says "my location" or "my address"
  • User says "where I live" or "my place"

DO NOT USE when user mentions a specific city/area (Bangalore, Koramangala, Mumbai) - use coordinates directly in search_restaurants_dineout instead.

WORKFLOW:

  1. Call this tool to get saved locations
  2. Show locations to user as numbered list
  3. Ask: "Which location would you like to search near?"
  4. Pass the chosen location's id as addressId in search_restaurants_dineout

RETURNS: List with index (1, 2, 3...), id, and addressLine for each saved address.

Next in this journey →

Continue with search_restaurants_dineout.