Crawlora MCP

zara_product

Read-only

One Zara product's full detail: every purchasable color variant with its real marketing description, per-size stock, and full image gallery -- richer than the per-product summaries from zara_category_products and zara_search. product_id is a numeric id, taken from a search/category result's url field (the digits after "-p" in the product-detail URL).

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": {
      "product_id": "<product_id>"
    },
    "name": "zara_product"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes	Required numeric Zara product ID in the 4–15 digit range, taken from a search/category result URL after -p.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / product_id / description

Added value: +"Required numeric Zara product ID in the 4–15 digit range, taken from a search/category result URL after -p."

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description earns credit for describing the actual payload: every purchasable color variant, its marketing description, per-size stock, and the image gallery. No auth or rate-limit notes are given, but as a read-only single-record fetch that is a minor gap.

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?

Two sentences, front-loaded with the payload description before the parameter sourcing detail. Every clause carries information; nothing is redundant padding.

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?

An output schema exists so returns needn't be explained, yet the description still previews the shape. With one fully documented required parameter and clear routing context, an agent has everything needed to invoke it 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 description coverage is 100% and the product_id field already documents the numeric range and the 'digits after -p' sourcing. The description restates the same sourcing rule, adding little beyond the schema, so the baseline of 3 is appropriate.

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 and resource ('One Zara product's full detail') and immediately names what the response contains. It explicitly distinguishes itself from the sibling summary tools zara_category_products and zara_search, so an agent can route 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?

Explicitly contrasts itself against zara_category_products and zara_search ('richer than the per-product summaries'), which tells the agent when this detail fetch is warranted. It stops short of stating an explicit when-not condition or prerequisite (e.g., 'requires a product_id obtained from those tools'), so it falls just under full coverage.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?