Crawlora MCP

zalando_search

Read-only

Search a Zalando country storefront by keyword and return normalized prices, brands, and images. Use zalando_suggest for typeahead, zalando_product for one item, or zalando_markets to choose a country storefront.

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": {
      "q": "<q>",
      "market": "<market>"
    },
    "name": "zalando_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Required. Product search keyword.
`market`	Yes	Required. Zalando country storefront: de, es, fr, gb, it, nl, pl, or se. See zalando_markets for the full list.

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.

First observedOct 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and reach are covered. The description adds that results are 'normalized' across storefronts, which is useful context, but says nothing about pagination, result caps, or locale/currency handling. Adequate but not rich beyond the annotations.

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?

Two sentences, zero waste, and the core capability is front-loaded before the routing hints. Every clause carries information an agent needs.

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?

With an output schema present, the description needn't enumerate return fields, and the annotation pair covers safety/openness. The remaining pieces an agent needs - what to pass, which storefront, and which sibling handles adjacent needs - are all present.

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% and both parameters are documented in-schema, including the market enumeration and the pointer to zalando_markets. The description only restates 'country storefront' and 'keyword', adding no syntax or format detail beyond the schema. Baseline 3.

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?

States a specific verb (Search), resource (Zalando country storefront), input scope (keyword) and even the shape of the result (normalized prices, brands, images). This clearly separates it from sibling tools like zalando_product and zalando_category without opening a schema.

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?

Explicitly routes the agent: zalando_suggest for typeahead, zalando_product for a single item, zalando_markets for picking a storefront. Both the when-to-use and the alternatives are named, leaving nothing to inference.

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.