Crawlora MCP

glovo_store_search

Read-only

Search one Glovo store's products by keyword and return the matching records with name, description, price, currency, image URL, stock flag and option groups, plus total_products. Requires country, city, store_id and query; pass address_id from glovo_stores to skip an extra lookup, and limit to cap results (default 50, maximum 500).

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>",
      "query": "<query>"
    },
    "name": "glovo_store_search"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug (madrid) or code (mad), from /glovo/cities.
`limit`	No	Optional max products returned. Defaults to 50, maximum 500.
`query`	Yes	Keyword to search this store's own products by, for example burger.
`country`	Yes	Two-letter country code, from /glovo/cities.
`language`	No	Optional two-letter response language; defaults to en.
`store_id`	Yes	Store id, from /glovo/stores' id field.
`address_id`	No	Optional store location id, from /glovo/stores' address_id field. When omitted the store's own default location is looked up first.

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.

AddedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, but the description adds useful behavior beyond them: the return fields, total_products, the address_id lookup shortcut, and the limit default and maximum. It does not discuss authentication, rate limits, or 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and contains no filler. It is dense and appropriately sized, though the return-field list is somewhat less necessary because an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, annotations, and full schema coverage, the description is complete enough for an agent to call it correctly. It covers required inputs, optional lookup shortcut, result cap, and returned data without omitting anything critical.

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, but the description adds cross-tool meaning by explaining that address_id comes from glovo_stores and skips an extra lookup. It also restates the limit cap and default, which is helpful though already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: search one Glovo store's products by keyword. It clearly distinguishes keyword search from a broad product listing, though it does not explicitly name the sibling tool glovo_store_products as the alternative.

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 gives clear usage context by listing required inputs and explaining that address_id from glovo_stores can skip an extra lookup. It does not explicitly say when not to use this tool or directly compare it with alternatives such as glovo_store_products.

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?