Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

swiggy_search

Search Swiggy restaurants delivering to any location, using keywords, cuisines, dishes, or curated collections, with filters for veg, rating, offers, and sorting.

Instructions

Search Swiggy restaurants near a location. Returns restaurants delivering to a latitude/longitude, optionally filtered by a keyword or browsed within a curated collection. With no query and no collection_id this browses the nearby-restaurant listing; with a query it runs a keyword search across restaurant names, cuisines, and dishes; with a collection_id (from /swiggy/collections) it browses restaurants within that curated collection. query and collection_id are mutually exclusive. Keyword search has two result tabs, selected with tab: dish (the default) returns restaurants that serve a matching dish, each with the matching dishes, their prices, and Swiggy's own per-dish rating where it has one, in a dishes array; restaurant returns restaurants whose own name or cuisine matches, a wider set with no dishes. tab, veg, min_rating and offers are only valid together with query. sort works with either query (relevance, delivery_time, rating) or collection_id (those three plus cost_low_to_high and cost_high_to_low), and is rejected on a plain nearby browse. Each restaurant carries its id (the value the restaurant and menu endpoints take), name, cuisines, cost for two, rating, delivery time, open/closed status, a hero image, and, where one is shown, an external_rating block with the third-party aggregate score, count, and source. Where the result card advertises a promotion it also carries offers, the same title/description/tag shape /swiggy/restaurant returns (a listing card never carries a coupon code, and a card showing both a discount and a separate free-delivery benefit returns them as two entries). is_promoted is present and true only for a result Swiggy itself labels a sponsored placement rather than an organic one. unavailable_message is present only when Swiggy says the restaurant cannot currently be ordered from and carries its own reason; it is not the inverse of is_open, since Swiggy reports a restaurant as open while still refusing orders for the requested location. A plain nearby browse also returns is_serviceable, which says whether Swiggy delivers to the requested coordinates at all: false means the coordinates are outside Swiggy's delivery coverage, so the empty restaurants list is a coverage answer rather than a no-matches answer, while an empty list without the field means no matches in a served area. It is omitted on keyword search and on a collection_id browse, neither of which carries Swiggy's own coverage marker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabNoWhich keyword-search result tab to read: dish (default, restaurants serving a matching dish, each with a dishes array) or restaurant (restaurants whose own name/cuisine matches). Only valid together with query.
vegNoOnly return vegetarian results: veg dishes on tab=dish, pure-veg restaurants on tab=restaurant. Only valid together with query.
sortNoOptional sort order. With query: relevance, delivery_time, rating. With collection_id: those three plus cost_low_to_high and cost_high_to_low. Not valid on a plain nearby browse.
queryNoOptional keyword to search restaurants and dishes by, at least 2 characters. Mutually exclusive with collection_id.
offersNoOnly return restaurants currently running an offer. Only valid together with query.
offsetNoOpaque pagination cursor from a prior response's next_offset (not meaningful when query is set)
latitudeYesSearch center latitude
longitudeYesSearch center longitude
min_ratingNoOnly return restaurants rated at or above this score (0-5). Only valid together with query.
collection_idNoOptional curated collection id from /swiggy/collections's id field. Browses restaurants within that collection instead of the plain nearby listing. Mutually exclusive with query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "relevance",
      +  "delivery_time",
      +  "rating",
      +  "cost_low_to_high",
      +  "cost_high_to_low"
      +]
    • addedInput schema / properties / tab / enum
      Added value: +[
      +  "dish",
      +  "restaurant"
      +]
  2. Addedv1.16.2

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully covers behavioral traits: result tabs, is_promoted semantics, unavailable_message meaning, is_serviceable distinction, and how empty lists should be interpreted. It explains field presence/absence conditions and edge cases, making the tool's behavior fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although long, the description is dense with necessary information and well-organized: it opens with purpose, then modes, then parameter constraints, then response fields. Every sentence adds value, and the structure is logical and front-loaded with the most critical usage decisions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, multiple modes, nuanced response fields, no output schema), the description is extremely complete. It covers all aspects an agent needs to correctly invoke the tool and interpret results, including edge cases like is_serviceable and unavailable_message.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 100% and each parameter has a description, the tool description adds significant context beyond the schema: mutual exclusivity of query and collection_id, valid combinations (tab/veg/min_rating/offers only with query), sort restrictions per mode, and offset semantics. This goes well beyond simple parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: searching Swiggy restaurants near a location, with three distinct modes (nearby browse, keyword search, collection browse). It uses specific verbs and resources, and distinguishes from siblings like swiggy_restaurant and swiggy_collections by explaining its scope and output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use each mode: with no query/collection_id for nearby browse, with query for keyword search, with collection_id for curated collections. It also states mutual exclusions (query vs collection_id), valid parameter combinations (tab, veg, min_rating, offers only with query), and sort restrictions. This is exceptional usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools