Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yoox_product

Fetch YOOX product data by item ID or legacy URL, including name, brand, price, stock, images, and category for catalog and price checks.

Instructions

Get a YOOX product. Returns a YOOX product by item id, the path segment before /item in a product URL, for example 17734181OO. The older url parameter still works instead. The response has name, brand, price, currency, in_stock, description, images and category. Calls can take up to about 80 seconds and return 503 if they cannot finish.

Input Schema

NameRequiredDescriptionDefault
idNoYOOX item id, for example 17734181OO
urlNoLegacy YOOX product URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses that calls can take up to ~80 seconds and return `503` on failure, which an agent needs for timeout/retry strategy. This is exactly the operational context annotations would otherwise provide.

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 tight sentences, front-loaded with purpose and id mechanics, then the response shape and latency/error note. The response-field enumeration is slightly list-heavy but everything earns its place.

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 detail tool with no output schema and no annotations, the description covers the return fields (name, brand, price, currency, in_stock, description, images, category), the latency budget, and the error mode, leaving no critical gap for correct invocation.

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 description coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by explaining how to derive `id` from a URL and clarifying that the older `url` parameter is an accepted alternative. It goes slightly beyond what the structured fields state.

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 ("Get a YOOX product") and pins down exactly what it returns by item `id`. The id derivation rule (path segment before `/item`) plus the legacy `url` fallback make it unambiguous versus siblings like yoox_search or yoox_categories.

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 through the id-extraction guidance ("the path segment before `/item` in a product URL") and the note that `url` still works, but there is no explicit when-to-use-this-vs-another-tool routing or statement of prerequisites. Adequate but incomplete.

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