Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_search

Search Zalando products by keyword and required country storefront to get first-page cards with price, brand, image, and total results.

Instructions

Search Zalando products. Searches a Zalando country storefront by keyword and returns result cards with price, brand, and image. Returns the first page of results 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

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.1/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 does well: it discloses the return shape (price, brand, image cards), the pagination limitation (first page + total_count only, no deeper paging), and the required-market constraint. It omits any rate-limit or error behavior, so it stops short of full disclosure.

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?

Three sentences, front-loaded with purpose, then return behavior, then the parameter constraint. Each sentence earns its place, though the market constraint could be folded more tightly.

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 2-parameter search tool with no output schema and no annotations, the description covers what an agent needs: return fields, pagination ceiling, and the required-market caveat. Rate-limit/error behavior is the only notable omission.

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, but the description adds real meaning: it flags market as required with no default and notes the 25 supported storefronts plus a pointer to zalando-markets. That goes beyond the enum's bare list.

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 (search) and resource (Zalando products) and immediately scopes it to a country storefront by keyword. This clearly positions it as the keyword entry point, distinguishable from siblings like zalando_product (detail) and zalando_suggest (autocomplete).

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?

Provides useful context that market is required with no default and points to zalando-markets for the storefront list, but never states when to choose this over zalando_suggest or zalando_product. Usage is implied rather than explicitly framed.

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