Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yoox_designers

Fetch YOOX designers for a department (women, men, kids) with names, slugs, and URLs. Use each slug as a designer parameter in YOOX search.

Instructions

List YOOX designers. Lists YOOX designers for the required department (women, men or kids), with the count and each designer's name, slug and URL. Every designer slug is valid as designer in YOOX search. A call that cannot finish within about 80 seconds returns 503, as does one made during YOOX maintenance.

Input Schema

NameRequiredDescriptionDefault
departmentYesDepartment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the return payload (count plus name/slug/URL), and two distinct failure modes (503 on ~80s timeout and 503 during YOOX maintenance). It omits anything about auth, rate limits, or ordering, but the timeout/maintenance disclosure is substantive.

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 front-loaded sentences that each carry information (scope, return shape, error behavior). The opening two clauses ('List YOOX designers. Lists YOOX designers...') are mildly redundant, keeping it just below a 5.

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 single-param list tool with no output schema and no annotations, the description covers the return shape and error behavior an agent needs. Nothing required to invoke or interpret the call is missing.

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 coverage is 100% and the single enum param is fully documented in the schema. The description restates the enum values (women/men/kids) but adds no syntax or semantics beyond what the schema already provides, so the 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 ('List') and resource ('YOOX designers') with the scoping dimension ('for the required department'). It also connects to the sibling ecosystem by noting designer slugs are valid as `designer` in YOOX search, letting an agent place it relative to yoox_search and yoox_product.

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?

Explains the required context (department selection) and the downstream use of results (slug feeds yoox_search's designer param), which tells an agent when this tool is the entry point. It does not name explicit when-not conditions or alternatives, so it falls short of a 5.

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