Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ubereats_store_menu

Retrieve an UberEats store's full menu by UUID, including section titles, items, descriptions, prices, and availability status for credential-free public data.

Instructions

Get an UberEats store menu. Returns the full menu for an UberEats store: section titles, items, item descriptions, prices, and availability status. Credential-free public UberEats data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesUberEats store UUID, as returned by the search endpoint's storeUuid field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the operation is credential-free (no auth needed) and lists the exact payload fields, signaling a safe read-only fetch. It lacks details on error handling or rate limits, but for a simple menu retrieval it provides meaningful 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 sentences, front-loaded with the action and resource. Every sentence adds value: the first states purpose, the second enumerates return contents and access mode. No wasted words.

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 a single parameter and no output schema, the description adequately explains what the tool returns and that it is public data. It doesn't discuss relationships to sibling ubereats tools, but it is complete enough for an agent to decide when a store menu is needed.

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 coverage is 100%, and the store_id parameter is already well described in the schema as the UUID from search's storeUuid field. The description does not add any parameter information, but since the schema fully covers semantics, the baseline of 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 gets an UberEats store menu, with a specific verb ('Get') and resource ('store menu'). It enumerates the exact content returned (sections, items, descriptions, prices, availability), which distinguishes it from sibling tools like ubereats_store and ubereats_store_reviews.

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 provides clear context by noting it is credential-free public data, which implies it is appropriate for public store menus without authentication. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of full 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