Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_product

Fetch normalized details for one Zalando product, including brand, description, images, and per-size price, availability, and GTIN using its SKU and required market.

Instructions

Get a Zalando product. Returns normalized product details for one Zalando product, including brand, description, images, and per-size price/availability/GTIN. Pass the sku returned by zalando-search or zalando-category; Zalando's own site search resolves the sku to its canonical product page. market is required and must match the storefront the sku was found in (there is no default, and a sku is generally only listed for sale on the market(s) that carry it) — see zalando-markets for the full reference list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesZalando product SKU (article number) from zalando-search or zalando-category
marketYesZalando country storefront the sku was found in

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.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: returns normalized product details, includes per-size price/availability/GTIN, and the market requirement with no default. However, it does not mention error handling (e.g., invalid sku) or rate limits, which would be helpful but are not critical for correct usage. It adds value beyond the schema by explaining the normalization and market coupling.

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?

The description is concise and well-structured, with the core action and return details first, followed by parameter guidance. It uses a single, readable sentence that avoids redundancy and front-loads the most important information.

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 has no output schema, the description adequately explains what the tool returns (normalized details including per-size data). It also covers how to obtain the sku and the market constraint. The only minor omission is behavior on invalid inputs, but the core usage is fully covered for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions for sku and market are minimal, but the tool description adds substantial meaning: sku must come from search/category, and market must match the storefront, with no default and a note that a sku is generally only listed on markets that carry it. This goes beyond the schema and clarifies the exact relationship between parameters, helping the agent avoid errors.

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?

The description clearly states the tool's function: 'Get a Zalando product' and specifies the output details (brand, description, images, per-size price/availability/GTIN). It also differentiates from siblings by indicating the sku comes from zalando-search or zalando-category, making its role distinct.

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 instructs when to use the tool: after obtaining a sku from zalando-search or zalando-category. It also provides critical usage context for the market parameter, explaining it must match the storefront where the sku was found and referencing zalando-markets for the full list. This gives clear guidance on when to use this tool versus alternatives.

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