Crawlora MCP

zalando_product

Read-only

Zalando product details: brand, description, images, and per-size price/availability/GTIN, resolved from a sku.

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": {
      "sku": "<sku>",
      "market": "<market>"
    },
    "name": "zalando_product"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	Yes	Required. Zalando product SKU (Zalando's own article number, e.g. ONM11A03W-A12) as returned by zalando_search or zalando_category in the sku field.
`market`	Yes	Required. Zalando country storefront: de, es, fr, gb, it, nl, pl, or se. Must match the market the sku was found in.

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 5, 2026

TDQS

A3.6/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, covering the safety profile, so the bar is lower. The description adds the useful dependency that the record is resolved from a sku and that pricing/availability are per-size. It says nothing about permissions, rate limits, or failure modes when the sku/market mismatch, so it adds only modest context.

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?

A single front-loaded sentence that names the resource first and packs the returned data into a compact clause with zero filler.

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?

An output schema exists, so return values need not be explained, and both params are fully documented in the schema with annotations covering safety. The description is sufficient for correct invocation; only the when-to-use routing to sibling tools is absent.

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% with two well-documented required params, so the baseline is 3. The description reinforces the sku input and the per-size output granularity but adds no syntax, format, or constraint detail beyond what the schema already provides.

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?

States a specific resource (Zalando product details) and enumerates the returned fields (brand, description, images, per-size price/availability/GTIN), plus how it is resolved (from a sku). This clearly marks it as a detail-lookup rather than a browse/search tool. It does not explicitly name the sibling it complements, so it falls short of a 5.

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 phrase 'resolved from a sku' implies the tool requires a sku already obtained elsewhere, which is implied usage, but the description never states when to use it versus zalando_search/zalando_category. The explicit routing guidance ('as returned by zalando_search or zalando_category', 'must match the market') lives in the schema, not the description.

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?