Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zomato_search

Find Zomato restaurants in a city, with optional keyword search and filters for sort and Pure Veg. Returns restaurant URLs, ratings, cost, and delivery details in clean JSON.

Instructions

Search Zomato restaurants in a city. Returns restaurants in a Zomato city, optionally filtered by a keyword. With no query this reads Zomato's own city-wide delivery listing, which pages through an opaque cursor (~12 restaurants per page: pass a response's next_cursor back as cursor until has_more is false, which marks the end of the city's listing) and accepts Zomato's own sort and Pure Veg filters; with a query it uses Zomato's own keyword search across restaurant names, dishes, and cuisines, which returns a single unpaginated result set. Each restaurant carries its url (the value the restaurant and menu endpoints take), name, cuisines, cost for two, rating, distance from the city location, delivery time, whether Zomato currently delivers from it, whether the placement is promoted (sponsored), and — on the plain city-wide listing — Zomato's own headline offer badges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesZomato public city slug, e.g. \
sortNoSort order for the city-wide listing (used only when query is omitted)
queryNoOptional keyword to search restaurant names, dishes, or cuisines by. Omit for the plain city-wide delivery listing.
cursorNoOpaque pagination cursor from a previous city-wide listing response's next_cursor. Carries its own sort/pure_veg selection, so pass it on its own.
pure_vegNoWhen true, restricts the city-wide listing to restaurants Zomato itself marks Pure Veg (used only when query is omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "popularity_desc",
+  "rating_desc",
+  "cost_asc",
+  "cost_desc"
+]
  2. Addedv1.16.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full responsibility. It discloses pagination behavior (opaque cursor, ~12 per page, has_more), sorting and Pure Veg filters, that query returns a single unpaginated result set, and enumerates all returned fields. This is thorough and leaves little to surprise.

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

Conciseness4/5

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

The description is long but every sentence adds value—purpose, mode differentiation, pagination, and return fields. It is front-loaded with the core purpose and keeps related details in a logical flow. Slightly dense, but not bloated.

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 five parameters, no output schema, and no annotations, the description covers all necessary context: the two operational modes, pagination mechanics, filter behavior, and the full set of returned fields. An agent has enough to call this correctly without further lookup.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful interaction semantics: cursor carries its own sort/pure_veg selection, sort and pure_veg are only used when query is omitted, and query searches names, dishes, cuisines. These go beyond the schema's per-field descriptions.

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 verb 'Search' and the resource 'Zomato restaurants in a city', and immediately distinguishes two modes (city-wide listing vs. keyword search). It also hints at related endpoints (restaurant and menu) that consume the returned url, helping separate this search tool from sibling detail tools.

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

Usage Guidelines4/5

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

It explicitly explains when to use the query parameter (keyword search) vs. when to omit it (city-wide listing), and describes pagination with cursor usage. It implies alternatives (restaurant/menu endpoints) but does not name them explicitly, so an agent must infer to use zomato_restaurant for details.

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