Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yoox_search

Search YOOX's public catalog with department, category, designer, color, size, price, sale, sort, and page filters to locate products.

Instructions

Search YOOX products. Searches or browses YOOX's public catalog with department, category, designer, color, size, price, sale, sort, and page filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search
pageNo1-based page
sizeNoSize filter
sortNoSort
colorNoColor filter
limitNoResults per page
on_saleNoSale items only
categoryNoCategory slug from yoox-categories
designerNoDesigner slug from yoox-designers
price_maxNoMaximum price
price_minNoMinimum price
departmentYesDepartment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It states the action (searches/browses) but does not disclose details like read-only nature, required department parameter, or return format. For a search tool, this is somewhat adequate but lacks explicit behavioral context beyond the basic operation.

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?

The description is a single concise sentence that front-loads the main action ('Search YOOX products') and then lists relevant filters. It is not overly verbose, though the second clause is a bit lengthy due to the enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameterscars, no output schema, and no annotations, the description is too thin. It does not explain the required 'department' field, how to combine filters, or what the response contains. An agent would need to infer search result behavior without explicit guidance, leaving significant gaps.

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?

The schema already documents all 12 parameters with 100% coverage, so the baseline is 3. The description lists many filter names (department, category, designer, color, size, price, sale, sort, page) but does not add new meaning beyond restating them; it merely summarizes the schema.

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?

The description states a specific verb ('Search') and resource ('YOOX products'), and clarifies it can also browse the public catalog. This clearly distinguishes it from siblings that search other brands or catalogs, even though no alternative YOOX-specific tool is named.

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 description gives clear context: it is for searching/browsing YOOX's public catalog with various filters. It does not explicitly mention when not to use it or compare to alternatives, but for a unique brand-specific search tool, the usage is effectively implied and unambiguous.

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