Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_product

Retrieve product details for one Zalando item via SKU and country market, including brand, description, images, and per-size price, availability, and GTIN.

Instructions

Get a Zalando product. Returns 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; 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

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.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 burden, and it delivers meaningful context: the full set of returned attributes and the non-obvious constraint that a sku is generally only listed on markets that carry it. It stops short of stating read-only status explicitly or describing error behavior when a sku/market mismatch occurs, so not a 5.

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?

Front-loads the purpose, then returns, then parameter usage. Dense and largely waste-free, though the long parenthetical about the market constraint could be tightened.

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 no output schema or annotations, the description compensates by listing returned fields and the required parameter pairing. It omits failure modes (missing sku in market, invalid market), which is a minor gap for a two-parameter lookup.

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), but the description adds genuine meaning: it names sku's source tools and stresses the sku–market coupling and the absence of a default market. That goes beyond the schema's brief field descriptions.

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+resource ('Get a Zalando product') and immediately enumerates what is returned (brand, description, images, per-size price/availability/GTIN). This clearly distinguishes it from the sibling zalando-search/zalando-category, which return SKUs rather than product detail.

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 tells the agent where the sku comes from (zalando-search or zalando-category) and that market is required, must match the originating storefront, and has no default. It also routes to zalando-markets for the reference list, giving clear when-to-use guidance and prerequisites.

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