PyScrappy

Overview Schema Source Related Servers Discussions Admin

Search Ubereats

search_ubereats

Find restaurants delivering in a specified city on Uber Eats, returning names, estimated delivery times, fees, and store URLs. Use the results to fetch detailed menus for any listed restaurant.

Instructions

Search Uber Eats for restaurants delivering in a given city, returning a ScrapeToolResult envelope whose data is a list of restaurant objects (typically name, eta, delivery fee, and store url).

Fetches live listings from Uber Eats over the network at call time; no API key is required. The data list is capped at max_results and each item's store url is the input for get_ubereats_menu. Alongside data, the envelope carries count, scraper, source_urls, and errors (non-fatal issues, each with a url and message). If the city is unrecognized or no restaurants are found, data is an empty list and count is 0.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	City name to search, as a string. Example: "London". No default (required).
`max_results`	No	Maximum number of restaurants to return, as an integer. Example: 10. Default 30.

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.

Changed2 schema fields changedJul 31, 2026

changedInput schema / properties / city / description

Previous value: -"City name, e.g. \"London\"."New value: +"City name to search, as a string. Example: \"London\". No default (required)."

changedInput schema / properties / max_results / description

Previous value: -"Maximum restaurants to return (default 30)."New value: +"Maximum number of restaurants to return, as an integer. Example: 10. Default 30."

Changed18 schema fields changedv1.3.3Jul 31, 2026

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

addedInput schema / properties / max_results / description

Added value: +"Maximum restaurants to return (default 30)."

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

removedInput schema / title

Removed value: -"search_ubereatsArguments"

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"
```

AddedJul 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that the tool makes a live network call, requires no API key, caps results at max_results, returns non-fatal errors in an envelope, and handles unrecognized cities with empty data and count 0. This is rich, accurate behavioral context.

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?

The description is two concise paragraphs with the purpose front-loaded in the first sentence. Every sentence adds value: output shape, network behavior, cap, error envelope, and edge cases. There is no fluff or repetition.

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?

The description covers input, output, error handling, edge cases, and the follow-on tool (get_ubereats_menu). It even explains the ScrapeToolResult envelope's fields. For a 2-parameter search tool, this is comprehensive and leaves no significant gap for an agent making the call.

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 reinforces that max_results caps the list and mentions edge-case behavior for the city parameter, but it does not materially add beyond the schema's parameter descriptions. No parameter descriptions are missing, but the description's contribution is marginal.

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 states a specific verb and resource: 'Search Uber Eats for restaurants delivering in a given city'. It also describes the return envelope (ScrapeToolResult with restaurant objects), which clearly differentiates it from siblings like scrape_zomato or search_amazon. The mention of get_ubereats_menu as the consumer of the returned URLs further clarifies its unique role.

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?

The description makes its usage context clear: it is for discovering Uber Eats restaurants in a city and provides the store URL for a downstream get_ubereats_menu call. It does not explicitly contrast with alternative scraping/search tools or state when not to use it, but the Uber Eats specificity and the downstream tool reference give enough guidance for the agent.

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