Skip to main content
Glama

zara_search

Read-only

Search Zara product listings by keyword within one department section (WOMAN, MAN, KID, HOME, or BEAUTY), with real offset-based pagination. Best-effort relevance search -- an obscure keyword may return Zara's own fallback results instead of an empty result. Requesting an offset beyond the available results returns a normal empty result with is_last_page true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "section": "<section>"
    },
    "name": "zara_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per request, 1 to 100, defaults to 24
queryYesSearch keyword
offsetNoZero-based result offset, defaults to 0
sectionYesDepartment section to search. Documented values: WOMAN, MAN, KID, HOME, BEAUTY.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per request, 1 to 100, defaults to 24"
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based result offset, defaults to 0"
    • addedInput schema / properties / query / description
      Added value: +"Search keyword"
    • addedInput schema / properties / section / description
      Added value: +"Department section to search. Documented values: WOMAN, MAN, KID, HOME, BEAUTY."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: the best-effort relevance behavior (an obscure keyword may yield Zara's fallback results rather than an empty set) and the offset-beyond-results edge case returning is_last_page=true. These are non-obvious behaviors an agent could not infer from the schema.

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 front-loaded sentences, each earning its place: purpose/scope, fallback behavior, and pagination edge case. No filler or repetition of the resource name.

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 an output schema covering return values and annotations covering the safety profile, the description supplies everything an agent needs: scope, section constraint, search reliability caveat, and pagination behavior. Nothing material is missing.

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 baseline is 3, but the description adds meaning beyond the schema for the offset parameter by explaining the out-of-range pagination behavior. The section values restate the schema, but the pagination semantics are a genuine addition.

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 (Zara product listings) plus the scoping constraint (one department section). It names the valid section values, letting an agent distinguish it from siblings like zara_product, zara_category_products, and zara_suggest without opening any schema.

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?

The section requirement and keyword scoping give clear context for when this tool applies, and the offset note clarifies pagination usage. It stops short of explicitly routing to alternatives (e.g., category browsing via zara_category_products), so no exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.