Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_search

Search Zalando products by keyword for a required country market and return normalized cards with price, brand, and image.

Instructions

Search Zalando products. Searches a Zalando country storefront by keyword and returns normalized result cards with price, brand, and image. Returns the first page of results as rendered by Zalando plus the upstream total_count; deeper pagination is not yet supported. 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

TableJSON Schema
NameRequiredDescriptionDefault
qYesProduct search keyword
marketYesZalando country storefront

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

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

With no annotations, the description carries the disclosure burden; it reveals that results are normalized cards with price/brand/image, that only the first page is returned plus total_count, and that deeper pagination is unsupported. This is strong for a read-only search tool, though it doesn't address error conditions or API-level limits.

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?

Three sentences with no filler: core action, return/limitation, then the key parameter constraint. The market requirement is placed where it will be noticed before a call is constructed.

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?

For a 2-parameter tool with fully described parameters and no output schema, this is complete: it covers what is returned, pagination behavior, and the required market context. An agent has what it needs to call the tool correctly.

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%, so the baseline is 3; the description adds value by noting market is required, there is no default storefront, and the canonical list lives in zalando-markets. This gives an agent more operational context than the enum alone.

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 the verb ('Search') and resource ('Zalando products') and clarifies it searches a country storefront by keyword, which distinguishes it from category/browse tools. It doesn't explicitly name sibling alternatives, so it stops short of the strongest differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: this is the keyword-search entry point for Zalando storefronts, and the market parameter is required with no default. It doesn't spell out when to prefer zalando_suggest or category tools, but the search-by-keyword framing is sufficient for most routing decisions.

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