Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ubereats_search

Search UberEats restaurants delivering to a location by coordinates, returning names, ratings, delivery estimates, cuisine tags, and images. Add a keyword for name, cuisine, or dish; omit it to browse.

Instructions

Search UberEats restaurants. Returns restaurants delivering to a location: name, rating, review count, delivery estimate, cuisine tags, and image. Pass a keyword to search by name/cuisine/dish, or omit it to browse the general feed for that location.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of restaurants to return, clamped to 50. Default 20
queryNoKeyword — restaurant name, cuisine, or dish
cursorNoOpaque pagination cursor from a previous keyword-search response
offsetNoResult offset for the location feed (used only when query is omitted). Default 0
latitudeYesDelivery search center latitude
longitudeYesDelivery search center longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the load. It discloses the return fields and the keyword-vs-browse behavior, but says nothing about pagination mechanics, result limits, or any auth/rate constraints beyond what the schema already implies.

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?

Two dense sentences, front-loaded with the action and return shape, followed by the parameter-level guidance. No filler.

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?

For a location-based search with no output schema and full schema coverage, it explains purpose, returns, and the query/omit branch adequately. The main gap is not addressing the sibling ubereats_feed, leaving the browse-vs-feed boundary unclear.

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%, so the schema already documents all six parameters. The description adds marginal value by framing query as name/cuisine/dish and clarifying that omitting it browses the feed, but cursor vs offset behavior is left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search UberEats restaurants') and enumerates the returned fields. However, it does not distinguish itself from the sibling ubereats_feed, which the 'omit query to browse the general feed' phrasing actually sounds like, leaving ambiguity about which tool owns the browse case.

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?

Gives clear conditional usage: pass a keyword to search name/cuisine/dish, or omit it to browse the location feed. It stops short of naming alternatives or exclusions, notably the sibling ubereats_feed, which is exactly the tool an agent would compare against.

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