Crawlora MCP

zalando_category

Read-only

Browse a Zalando category or brand listing by URL slug and return the same normalized result cards as zalando_search.

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": {
      "category": "<category>",
      "market": "<market>"
    },
    "name": "zalando_category"
  }
}

Input Schema

Name	Required	Description	Default
`market`	Yes	Required. Zalando country storefront: de, es, fr, gb, it, nl, pl, or se. See zalando_markets for the full list.
`category`	Yes	Required. Zalando category or brand slug, e.g. shoes, womens-dresses, on-running, adidas. See zalando_categories for a market's discoverable top-level slugs.

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

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, so the safety profile is covered. The description usefully adds that output matches zalando_search's normalized result cards, aiding consistency expectations, but says nothing about pagination or depth of the listing.

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 dense sentence that front-loads the action and resource and closes with the output-compatibility note. No 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?

With an output schema present and 100% parameter documentation, the description only needs to establish purpose and routing, which it mostly does. Only minor gaps remain around pagination/filtering behavior for large category listings.

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%, so both parameters are fully documented in the schema. The phrase 'by URL slug' reinforces the format of the category parameter but adds no syntax or constraint detail beyond what the schema already provides; baseline 3 applies.

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 verb (browse), resource (Zalando category or brand listing), input mechanism (URL slug), and output shape (same normalized result cards as zalando_search). An agent can distinguish it from zalando_search at a high level, though the boundary between 'browse by slug' and 'search' is only implied rather than spelled out.

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?

Usage is implied: reach for this when you have a category or brand slug rather than a free-text query. There is no explicit statement of when to prefer this over zalando_search vs zalando_categories, and no conditions or exclusions given.

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.