PyScrappy

Overview Schema Source Related Servers Discussions Admin

Get Ubereats Menu

get_ubereats_menu

Retrieve a restaurant's live Uber Eats menu from its store URL, returning item names, descriptions, and prices.

Instructions

Fetch an Uber Eats restaurant's live menu from its store URL and return the menu items with their names, descriptions, and prices.

Scrapes the restaurant page over the network at call time, so results reflect current listings and require internet access. Prices and availability depend on the store's configured location and hours. Returns a structured list of menu items (typically grouped by section/category); if the URL is invalid, the restaurant is unavailable, or the menu is empty, an empty result (no items) is returned rather than an error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`store_url`	Yes	URL string of the Uber Eats store page, taken from a search_ubereats result's "url" field. Example: "https://www.ubereats.com/store/some-restaurant/abc123". No default (required).

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.

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / store_url / description

Previous value: -"A store URL from a search_ubereats result's \"url\" field."New value: +"URL string of the Uber Eats store page, taken from a search_ubereats result's \"url\" field. Example: \"https://www.ubereats.com/store/some-restaurant/abc123\". No default (required)."

Changed16 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / store_url / description

Added value: +"A store URL from a search_ubereats result's \"url\" field."

removedInput schema / properties / store_url / title
```
Removed value: -"Store Url"
```

removedInput schema / title

Removed value: -"get_ubereats_menuArguments"

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
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, the description fully discloses behavior: it scrapes live, requires internet, reflects current listings, depends on location/hours, returns a structured list grouped by category, and returns empty results on error scenarios (invalid URL, unavailable, empty menu). This covers the key behavioral traits an agent would need to know, including error handling, without any contradictions.

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 three sentences, each earning its place: purpose, behavior (scraping, network, variability), and error handling. It's front-loaded with the primary action and efficiently conveys all necessary details without fluff. No redundant information.

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 presence of an output schema and a well-documented parameter, the description is complete for an agent to invoke the tool correctly. It explains network requirements, result structure, error behavior, and data dependencies. No missing critical information is apparent.

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?

The schema description covers the parameter 100%, already specifying the URL format and source (from search_ubereats). The description's reference to 'store URL' adds no new meaning beyond the schema. Since schema coverage is high, the baseline is 3; the description does not compensate with additional param details, so 3 is appropriate.

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 fetches a live menu from a store URL and returns item names, descriptions, and prices. It uses a specific verb ('fetch') and resource ('Uber Eats restaurant's live menu'), distinguishing it from generic scraping tools like scrape_url and search tools like search_ubereats. No ambiguity.

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 implies usage by referencing a 'store URL' and the need to scrape over the network, but it does not explicitly state when to use this tool versus alternatives. The input schema clarifies the URL comes from search_ubereats results, which provides context, but the description itself lacks explicit when/when-not guidance. Slightly below excellent because it doesn't name the alternative or condition explicitly.

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