get_restaurant_details

Swiggy Dineout: Get details about a specific restaurant for TABLE BOOKING. Returns ratings, deals, timings, address. Use restaurant ID from search_restaurants_dineout results. Use same coordinates th...

See get_restaurant_details in actionComing soon

Example

const result = await client.callTool({
  name: "get_restaurant_details",
  arguments: {
    restaurantId: "rest_42",
    latitude: 12.9716,
    longitude: 77.5946,
  },
});

Parameters

Parameter	Type	Required	Description
`restaurantId`	`string`	yes	Restaurant ID from search results
`latitude`	`number`	yes	Latitude (use same as search)
`longitude`	`number`	yes	Longitude (use same as search)

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

Success:

{
  "success": true,
  "data": { /* full restaurant details object */ },
  "latitude": 12.9716,
  "longitude": 77.5946,
  "message": "Restaurant details retrieved successfully."
}

data — full restaurant details (ratings, deals, timings, address, etc.).
latitude / longitude — top-level convenience fields echoing the input coordinates. Pass them directly to downstream tools (get_available_slots, book_table) without extracting from data.

On failure the server wraps the error in the standard envelope:

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

See Error codes for the full catalogue.

Details

Field	Value
Name	`get_restaurant_details`
MCP Server	Dineout
Endpoint	`POST mcp.swiggy.com/dineout`
Stage	Find
Behaviour	read-only

Next in this journey →

Continue with get_available_slots.