Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

glovo_store_menu

Retrieve a Glovo store's menu as collections such as Top sellers, Starters, and Drinks, with each collection slug usable as the value for the store products endpoint.

Instructions

Get one Glovo store's menu collections. Returns one store's menu as its tree of collections (for example Top sellers, Starters, Drinks). Each collection's slug is the value /glovo/store/products takes as collection. When address_id is omitted the store's own default location is looked up first, which costs one extra upstream call.

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": {
      "country": "<country>",
      "city": "<city>",
      "store_id": "<store_id>"
    },
    "name": "glovo_store_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug (madrid) or city code (mad), from /glovo/cities.
countryYesTwo-letter country code, from /glovo/cities.
languageNoOptional two-letter response language; defaults to en. A city's supported languages are in /glovo/city's supported_languages.
store_idYesStore id, from /glovo/stores' id field.
address_idNoOptional store location id, from /glovo/stores' address_id field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden. It discloses the return shape as a tree of collections, gives examples, and warns that omitting address_id causes an extra upstream lookup. It does not cover auth, rate limits, or empty-menu/error behavior.

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?

Three sentences, front-loaded with the core purpose and return shape. The examples and address_id caveat are useful and earn their place.

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 no output schema and no annotations, the description still explains the return structure and a key operational caveat. It lacks full response-shape and error-behavior detail, but is adequate for a menu-retrieval tool.

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 the baseline is 3. The description adds meaning beyond the schema by linking collection slugs to /glovo/store/products and explaining the cost/behavior change when address_id is omitted.

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: getting one Glovo store's menu collections. It also distinguishes the result from product listing by explaining that collection slugs are what /glovo/store/products consumes.

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 clearly implies the workflow: use this tool to obtain collection slugs before calling /glovo/store/products. It does not explicitly state when not to use it or name sibling alternatives, so it falls short of a 5.

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