Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zara_search

Search Zara product listings by keyword within a chosen department using offset pagination, returning pricing, images, availability, color variants, and search facets.

Instructions

Search Zara products. Searches Zara product listings by keyword within one department section, with real offset-based pagination. Returns products with pricing, images, availability, and every purchasable color variant, plus the search facets. This search is best-effort relevance, not a guaranteed keyword match: for an obscure or nonsense keyword, Zara's own search falls back to a broader recommended result set instead of returning an empty list, and there is no reliable field in the response to distinguish a true keyword match from that fallback behavior. Requesting an offset beyond the available results returns a normal, empty result with is_last_page true rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per request, 1 to 100, defaults to 24
queryYesSearch keyword
offsetNoZero-based result offset, defaults to 0
sectionYesDepartment section to search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / section / enum
      Added value: +[
+  "WOMAN",
+  "MAN",
+  "KID",
+  "HOME",
+  "BEAUTY"
+]
  2. Addedv1.14.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses offset-based pagination, the best-effort relevance fallback to recommended results for nonsense keywords, the absence of a reliable match-vs-fallback field, and that out-of-range offsets yield an empty result with is_last_page true rather than an error.

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?

Purpose and pagination are front-loaded, and the fallback/pagination caveats are genuinely useful rather than filler. It runs a bit long, with the fallback caveat spread across two clauses that could be tightened, but every sentence contributes.

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?

With no output schema, the description steps in to summarize the return payload (pricing, images, availability, every purchasable color variant, plus facets) and clarifies edge-case pagination behavior. An agent has everything it needs to call this correctly.

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

Parameters3/5

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

Schema coverage is 100%, so limit, query, offset, and section are already documented in the schema; baseline is 3. The description adds the pagination model and reinforces the one-section constraint but no per-parameter detail beyond what the schema provides.

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?

It opens with a specific verb+resource ("Search Zara products") and immediately scopes it: keyword search within a single department section. This cleanly separates it from the sibling product/category/store tools (zara_product, zara_category_products, zara_stores) without needing to name them.

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?

Usage is implied rather than stated: the agent can infer it is the tool for keyword search within a section. There is no explicit when-to-use vs. alternatives (e.g., zara_suggest, zara_category_products) and no when-not-to-use guidance, so it stays at the minimum-viable level.

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