Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deliveroo_search

Search Deliveroo restaurants, groceries, or shopping stores near any location. Returns the full catalog feed for a latitude/longitude with filters for cuisine, rating, delivery time, and more.

Instructions

Search Deliveroo restaurants, groceries, or shopping stores near a location. Returns the restaurants (or, with collection set, grocery/shopping stores) Deliveroo's own catalog serves for a latitude/longitude in the given market -- the location's entire feed, not a curated subset (confirmed live: up to 2,700+ results for a single coordinate). Each result carries its uname (the value the restaurant and menu endpoints take), name, image, branch_type, and, when available, rating, delivery time, and distance. Optional collection, cuisine, dietary, dish, min_rating, max_delivery_minutes, max_delivery_fee_pounds, has_offer, deliveroos_choice, and sort parameters narrow and order the same feed -- call /deliveroo/search/filters for the current, complete, location-scoped list of every valid cuisine/dietary/dish value with live result counts. A location with no coverage returns an empty list rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dishNoOptional, repeatable Deliveroo dish-level filter passed straight through to the upstream, e.g. dish=pizza&dish=sushi. Call /deliveroo/search/filters for the current, complete, location-scoped list of valid values. An unrecognized value is silently ignored by the upstream, not rejected.
sortNoResult ordering
limitNoRestaurants to return, clamped to 100 (default 20)
marketNoDeliveroo national market to search (default uk)
cuisineNoOptional, repeatable Deliveroo cuisine filter, e.g. cuisine=american&cuisine=asian. Passed straight through to the upstream; call /deliveroo/search/filters for the current, complete, location-scoped list of valid values. An unrecognized value is silently ignored by the upstream, not rejected.
dietaryNoOptional, repeatable Deliveroo dietary filter passed straight through to the upstream, e.g. dietary=vegan. Call /deliveroo/search/filters for the current, complete list of valid values. An unrecognized value is silently ignored by the upstream, not rejected.
latitudeYesSearch center latitude
has_offerNoWhen true, only returns results currently running an offer/promotion
longitudeYesSearch center longitude
top_ratedNoWhen true, only returns results Deliveroo itself marks top-rated (its own 4.5+ threshold). Equivalent to min_rating=4.5; ignored if min_rating is also set.
collectionNoOptional, passed straight through to the upstream. Selects the Deliveroo partner vertical: omit for restaurants/takeaways (default), grocery for supermarkets and convenience stores, shopping for non-food retail -- both confirmed live; other values may exist and are not rejected. Every result uses the same uname contract for /deliveroo/restaurant and /deliveroo/restaurant/menu.
min_ratingNoMinimum star rating filter
deliveroos_choiceNoWhen true, only returns results in Deliveroo's own Deliveroo's Choice curated collection. Combines with collection (e.g. collection=grocery&deliveroos_choice=true narrows to Deliveroo's Choice within the grocery vertical) rather than conflicting with it.
max_delivery_minutesNoMaximum estimated delivery time in minutes
max_delivery_fee_poundsNoMaximum delivery fee in GBP

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.17.5
    • addedInput schema / properties / cuisine / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / dietary / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / dish / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / market / enum
      Added value: +[
+  "uk",
+  "ie",
+  "fr",
+  "it",
+  "be",
+  "ae",
+  "kw"
+]
    • addedInput schema / properties / max_delivery_fee_pounds / enum
      Added value: +[
+  1,
+  2,
+  3
+]
    • addedInput schema / properties / max_delivery_minutes / enum
      Added value: +[
+  20,
+  30,
+  45
+]
    • addedInput schema / properties / min_rating / enum
      Added value: +[
+  3.5,
+  4,
+  4.5
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "recommended",
+  "distance",
+  "time",
+  "rating"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses several behavioral traits: returns up to 2,700+ results (scale), returns an empty list rather than error for no coverage, and that filters are passed through to upstream (though schema notes silent ignoring). It also states the result fields. It does not mention auth, rate limits, or read-only status, but for a search API these are less critical. The disclosed traits are meaningful and go beyond basic function.

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 concise but information-dense, with the core purpose front-loaded. Each sentence earns its place: search scope, feed nature, result fields, filter usage, and edge-case behavior. No fluff or redundancy. Well-structured and skimmable.

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 tool with 15 parameters and no output schema, the description covers the essential usage: result fields, uname contract for downstream calls, filter endpoint for valid values, and empty-list behavior. It does not explain pagination or limit effects (schema covers limit), nor the exact output format, but these are either in schema or less critical. Overall sufficient for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying that optional parameters narrow and order the same feed, not a separate curated list. It also explains that the collection parameter selects verticals (grocery/shopping) with examples, and that uname is the key for downstream endpoints. This enriches understanding beyond the schema's property descriptions.

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 searches Deliveroo restaurants, groceries, or shopping stores near a location, specifying the action (search), resource (restaurants/groceries/shopping), and inputs (latitude/longitude). It further distinguishes from siblings by explaining it returns the entire feed, not a curated subset, and mentions the uname contract linking to restaurant/menu endpoints. This is unambiguous and differentiates from deliveroo_restaurant and deliveroo_search_filters.

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?

It tells the agent to call /deliveroo/search/filters for valid cuisine/dietary/dish values, which is a clear pointer to a sibling for filter validation. It also implies the flow: use this search to get unames, then use restaurant/menu endpoints. However, it does not explicitly exclude other search-like tools (e.g., foodpanda_search) or state when this is the preferred search, though the context makes it obvious. Slightly short of explicit when-not 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