Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_category

Browse a Zalando category or brand listing by URL slug and market to retrieve product cards and the category's total count.

Instructions

Browse a Zalando category or brand. Browses a Zalando category or brand listing by URL slug (e.g. shoes, womens-dresses, on-running) and returns the same result cards as zalando-search, plus the category's upstream total_count. Category slugs are market-specific (each storefront uses its own local-language slug, e.g. "shoes" on de/gb, "chaussures" on fr, "scarpe" on it) — use zalando-categories to discover a market's live top-level slugs, or take one from a product's url field. market is required (there is no default storefront) and accepts 25 country storefronts — see zalando-markets for the full current list with domains.

Input Schema

NameRequiredDescriptionDefault
marketYesZalando country storefront
categoryYesZalando category or brand URL slug, in the target market's own language

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "hr",
+  "hu",
+  "ie",
+  "it",
+  "lt",
+  "lu",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "ro",
+  "se",
+  "si",
+  "sk"
+]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses useful behavior: it returns the same result cards as zalando-search plus the category's upstream total_count, and it warns that slugs are market-specific so a valid slug in one storefront won't work in another. It stops short of covering pagination, limits, or auth requirements, so it is informative but not complete.

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 dense but well-structured and front-loaded, leading with the core action before covering slug semantics and market requirements. Nearly every sentence earns its place, though it runs somewhat long.

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?

For a multi-market browse tool with no output schema and no annotations, the description adequately explains the return shape, the mandatory market parameter, and the market-specific slug requirement. The main remaining gap is pagination/result-count behavior beyond total_count.

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% (baseline 3), and the description adds real value beyond the schema by giving concrete slug examples (shoes, womens-dresses, on-running) and clarifying the market-specific, local-language nature of the category slug. It also reinforces that market is mandatory with 25 valid storefronts.

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 (browse) and resource (Zalando category or brand listing) and clarifies it works by URL slug. It explicitly names sibling tools it is related to (zalando-search, zalando-categories, zalando-markets), so an agent can distinguish it 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?

Gives explicit routing guidance: use zalando-categories to discover a market's live slugs, or take a slug from a product's url field. It also states the key prerequisite that market is required with no default storefront, removing ambiguity about when the tool can be called.

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