Crawlora MCP

ubereats_search

Read-only

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. Credential-free public UberEats data. cursor: Opaque pagination cursor from a previous keyword-search response (used only when query is set). latitude: Delivery search center latitude (required). Use ubereats_feed to browse UberEats location feed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "ubereats_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of restaurants to return, clamped to 50. Default 20.
`query`	No	Optional keyword — restaurant name, cuisine, or dish. Omit to browse the general feed for the location.
`cursor`	No	Opaque pagination cursor from a previous keyword-search response (used only when query is set).
`offset`	No	Result offset for the location feed (used only when query is omitted). Default 0.
`latitude`	Yes	Delivery search center latitude (required).
`longitude`	Yes	Delivery search center longitude (required).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds meaningful context beyond them: 'credential-free public UberEats data' and the field-level shape of results. It stops short of explaining pagination behavior or limits, but adds real value over the annotations.

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?

Front-loaded with the outcome and return fields before the mode guidance, and no wasted sentences. It is slightly padded by re-stating cursor and latitude semantics already present in the schema.

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?

With an output schema present, the description needn't explain return values, yet it usefully summarizes the result fields. Required location params and the search/browse duality are covered; only pagination mechanics and the ubereats_feed-vs-omit-query distinction are left thin.

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 schema already documents all six parameters, including cursor/latitude semantics that the description merely repeats. Baseline 3 is appropriate since the description adds no syntax or constraint details beyond the structured fields.

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?

States a specific verb and resource (returns restaurants delivering to a location), enumerates the returned fields, and distinguishes the two modes (keyword search vs. browsing). It also names the sibling ubereats_feed, so an agent can tell it apart from related tools without opening schemas.

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 a clear conditional: pass a keyword to search, omit it to browse the general feed. It names ubereats_feed as the alternative for browsing. However, the dual browse paths (omit query here vs. use ubereats_feed) are not fully disambiguated, leaving a small choice ambiguity.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?