PyScrappy

Overview Schema Source Related Servers Discussions Admin

Scrape Zomato

scrape_zomato

Find restaurants in any city on Zomato by scraping live listings, with optional cuisine or name filter and result cap. Returns structured restaurant records with ratings, price, address, and URL.

Instructions

Search Zomato for restaurants in a city and return a list of restaurant records.

Scrapes Zomato's public restaurant listings over the network for the given city, optionally filtered by a cuisine or name term. Each result is a dict with fields such as name, cuisine, rating, price_for_two, address, and url; the exact keys depend on what Zomato exposes for each listing. Returns a list of these dicts ordered as Zomato ranks them, capped at max_results. Returns an empty list if the city is unknown or no restaurants match the query. Requires outbound network access; results reflect live Zomato data at call time and may vary between calls.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	Yes	String city name to search within. Example: "Bangalore". Required, no default.
`query`	No	Optional string cuisine or restaurant search term to filter results. Example: "biryani". Defaults to None (returns all restaurants for the city).
`max_results`	No	Integer maximum number of restaurants to return. Example: 20. Defaults to 50.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 31, 2026

changedInput schema / properties / city / description

Previous value: -"City name, e.g. \"Bangalore\"."New value: +"String city name to search within. Example: \"Bangalore\". Required, no default."

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of restaurants to return (default 50)."New value: +"Integer maximum number of restaurants to return. Example: 20. Defaults to 50."

changedInput schema / properties / query / description

Previous value: -"Optional cuisine or restaurant search term."New value: +"Optional string cuisine or restaurant search term to filter results. Example: \"biryani\". Defaults to None (returns all restaurants for the city)."

Changed20 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / city / description
```
Added value: +"City name, e.g. \"Bangalore\"."
```
removedInput schema / properties / city / title
```
Removed value: -"City"
```

addedInput schema / properties / max_results / description

Added value: +"Maximum number of restaurants to return (default 50)."

removedInput schema / properties / max_results / title
```
Removed value: -"Max Results"
```

addedInput schema / properties / query / description

Added value: +"Optional cuisine or restaurant search term."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

removedInput schema / title

Removed value: -"scrape_zomatoArguments"

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

Addedv1.2.0Jul 26, 2026
Removedv1.1.7Jul 26, 2026
First observedv1.1.6Jul 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full transparency burden and does well: it discloses outbound network dependency, live-data variability between calls, result ordering, capping by max_results, and the empty-list behavior. It does not mention potential rate limits or blocking, but the provided behavioral caveats are substantial and useful.

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 well-structured and front-loaded, with the core purpose in the first sentence followed by behavioral details. There is mild redundancy between 'Search Zomato...' and 'Scrapes Zomato's public restaurant listings...', but overall every sentence earns its place and no extraneous content appears.

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

Completeness4/5

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

Given the presence of an output schema and the tool's straightforward parameter set, the description is complete enough: it covers return shape, ordering, capping, unknown-city behavior, no-match behavior, and network requirements. Minor gaps like pagination or error modes are not critical for this tool's complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds minimal meaning beyond the schema: it restates the query filter as 'cuisine or name term' and says results are 'capped at max_results', but most parameter meaning (examples, defaults, types) already lives in the structured schema.

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 first sentence states a specific verb and resource: 'Search Zomato for restaurants in a city and return a list of restaurant records.' This clearly differentiates the tool from siblings like scrape_wikipedia, scrape_stock, and search_ubereats by naming the exact platform, data type, and action.

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

Usage Guidelines3/5

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

The description implies usage: use this when you need Zomato restaurant listings for a city, optionally filtered by cuisine/name. However, it never explicitly contrasts this tool with alternatives like scrape_url or search_ubereats, nor states when not to use it. The usage context is clear but the decision guidance is left to inference.

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