Crawlora MCP

yoox_search

Read-only

Search YOOX products using department, category, designer, color, size, price, sale, sort, and page filters. Use yoox_designers to discover designers for one department, yoox_categories for category IDs, or yoox_product for one item.

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": {
      "department": "<department>"
    },
    "name": "yoox_search"
  }
}

Input Schema

Name	Required	Description
`q`	No	Free-text search
`page`	No	1-based page
`size`	No	Size filter
`sort`	No	Sort. Documented values: relevance, newest, price_asc, price_desc, discount.
`color`	No	Color filter
`limit`	No	Results per page
`on_sale`	No	Sale items only
`category`	No	Category slug from yoox-categories
`designer`	No	Designer slug from yoox-designers
`price_max`	No	Maximum price
`price_min`	No	Minimum price
`department`	Yes	Department. Documented values: women, men, kids.

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.

Changed12 schema fields changedOct 7, 2026
- addedInput schema / properties / category / description
```
Added value: +"Category slug from yoox-categories"
```
- addedInput schema / properties / color / description
```
Added value: +"Color filter"
```
- addedInput schema / properties / department / description
```
Added value: +"Department. Documented values: women, men, kids."
```
- addedInput schema / properties / designer / description
```
Added value: +"Designer slug from yoox-designers"
```
- addedInput schema / properties / limit / description
```
Added value: +"Results per page"
```
- addedInput schema / properties / on_sale / description
```
Added value: +"Sale items only"
```
- addedInput schema / properties / page / description
```
Added value: +"1-based page"
```
- addedInput schema / properties / price_max / description
```
Added value: +"Maximum price"
```
- addedInput schema / properties / price_min / description
```
Added value: +"Minimum price"
```
- addedInput schema / properties / q / description
```
Added value: +"Free-text search"
```
- addedInput schema / properties / size / description
```
Added value: +"Size filter"
```
- addedInput schema / properties / sort / description
```
Added value: +"Sort. Documented values: relevance, newest, price_asc, price_desc, discount."
```
First observedOct 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read. The description adds only the filter enumeration, which largely restates params, and says nothing about pagination behavior, result caps, or rate limits beyond what the schema already conveys.

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, no waste: the capability statement comes first and the cross-tool routing second. Every clause earns its place.

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 12-parameter search tool with an existing output schema and safety annotations, the description covers purpose and sibling routing adequately. It could mention the required department or paging expectations, but the schema and output schema carry that load.

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%, so every one of the 12 parameters is documented in the schema itself, including enums for sort and department. The description's listing of filter names adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 ('YOOX products'), then enumerates the filter dimensions (department, category, designer, color, size, price, sale, sort, page). It also names the sibling tools so the agent can distinguish this from yoox_product and yoox_categories without opening schemas.

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 routes the agent to yoox_designers for designer discovery, yoox_categories for category IDs, and yoox_product for a single item. This covers alternatives clearly, though it doesn't state a when-not condition for this tool itself or note that department is required.

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.