Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

doordash_search_items

Search DoorDash menu items by query and location to find which nearby merchants sell them. Get matching items with parent store info; no account required.

Instructions

Search DoorDash dishes and items. Searches menu items across nearby merchants from the Android mobile guest experience. Nearby candidate stores are selected first, then their menus are read and every item whose name or description matches the query is returned with its parent store. At most five proximity-ranked stores are inspected per request, and a store whose menu cannot be read is skipped, so results are best-effort across that candidate set. An empty result array means no candidate store menu matched, not that no nearby merchant sells the item. No DoorDash account or caller-supplied token is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoCuisine or store tag used to narrow candidate stores
queryYesDish or item search text
asapOnlyNoKeep only stores currently available ASAP
latitudeYesConsumer latitude
longitudeYesConsumer longitude
pickupOnlyNoKeep only pickup-enabled stores
dashPassOnlyNoKeep only DashPass-eligible stores
maxDistanceMilesNoMaximum displayed distance in miles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.16.2
    • addedInput schema / properties / asapOnly
      Added value: +{
+  "description": "Keep only stores currently available ASAP",
+  "type": "boolean"
+}
    • addedInput schema / properties / dashPassOnly
      Added value: +{
+  "description": "Keep only DashPass-eligible stores",
+  "type": "boolean"
+}
    • addedInput schema / properties / maxDistanceMiles
      Added value: +{
+  "description": "Maximum displayed distance in miles",
+  "type": "number"
+}
    • addedInput schema / properties / pickupOnly
      Added value: +{
+  "description": "Keep only pickup-enabled stores",
+  "type": "boolean"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Search text"New value: +"Dish or item search text"
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Cuisine or store tag used to narrow candidate stores",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries its own weight and does so well: it discloses the best-effort candidate-set approach, the five-store inspection limit, unreadable stores being skipped, the meaning of an empty result array, and that no account or caller-supplied token is needed. This is far beyond typical transparency and lets an agent correctly interpret missing results.

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?

Every sentence adds distinct information: the core action, candidate-store selection, result matching, the five-store limit, best-effort/empty-result caveats, and authentication. The description is front-loaded with the verb and resource and remains free of filler or repetition.

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 there is no output schema and no annotations, the description covers the essential context: what the tool searches, how stores are sampled, what empty results mean, and that no auth is needed. It doesn't describe the exact output fields beyond 'parent store', but the remaining uncertainty is minor for a search tool of this kind.

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 baseline of 3 applies. The description adds contextual meaning—query matches item name/description and nearby merchants are proximity-ranked—which helps interpret query and latitude/longitude. It does not add per-parameter syntax, but that is already well-covered by the schema 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 opens with a precise action—'Search DoorDash dishes and items'—and then explains the exact mechanism: candidate nearby stores are selected, their menus read, and matching items returned with their parent store. This clearly distinguishes it from siblings like doordash_search or doordash_search_autocomplete by focusing on menu-item matching across a proximity-ranked store set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage—searching menu items across nearby merchants from the Android guest experience—but it never explicitly says when to prefer this tool over doordash_search, doordash_store_menu, or other siblings. There are no exclusions or when-not-to-use conditions. The context is clear enough to infer, but the guidance is not explicit.

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