Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

starbucks_menu

Fetch the complete Starbucks menu as a category tree, including products, sizes, and availability. Optionally filter by store number or market to show what a specific location carries.

Instructions

Browse the full Starbucks menu. Returns Starbucks' full menu as a category tree: top-level categories, their child categories, and every product with its product number, form, product type, sizes, default size, availability, and image. Pair a product's product_number and form with /starbucks/product to fetch full detail including nutrition. store_number optionally scopes the menu to one store, using a store number from /starbucks/stores; a store-scoped menu marks items that store does not carry with availability NotAvailableHere, while the unscoped menu reports everything as Available. market selects which country catalog to return, one of us or ca, defaulting to us; the two differ substantially (roughly 282 US products vs 253 CA, with exclusives on both sides). Only these two markets are available: every other Starbucks country site runs a different platform, and the European ones disallow API access in robots.txt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoStarbucks country site to read. One of: us, ca. Defaults to us
store_numberNoStarbucks store number to scope availability to, e.g. 101-54

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "us",
+  "ca"
+]
  2. Addedv1.16.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations are absent, so the description carries the full burden, and it does so well: it discloses the output structure, the availability behavior difference between store-scoped and unscoped menus, and the substantial catalog differences between markets. It does not explicitly state read-only/no side effects or error behavior, but 'Browse' and 'Returns' make the read-only nature reasonably clear.

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 dense but every clause earns its place: purpose, return shape, related tool, store scoping semantics, and market constraints are each addressed in logical order with no filler. It is appropriately sized for the complexity of the tool.

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 no output schema and no annotations, the description is quite complete: it names the output fields, references related tools, and explains the availability and market edge cases. Minor gaps remain around invalid store numbers, market/store interaction, and explicit error behavior, but these are not essential for a low-complexity two-optional-param browse tool.

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

Parameters5/5

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

Although the schema already describes both parameters (100% coverage), the description adds substantial meaning: store_number's effect is precisely explained as marking items NotAvailableHere vs Available, and market is given rich context about defaults, product-count differences, exclusives, and platform restrictions. This goes well beyond the enum and example in the schema.

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 states a specific verb and resource ('Browse the full Starbucks menu') and goes further by specifying the exact return shape: a category tree with child categories and product fields. It also distinguishes itself from starbucks_product by directing agents to pair a product_number and form with that tool for full detail, so siblings are clearly separated.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: use /starbucks/product for full product detail including nutrition, get store numbers from /starbucks/stores, and know that market is limited to us or ca. It even warns against other markets because they run different platforms or block API access, which helps an agent avoid invalid calls.

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