Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gucci_recommendations

Fetch Gucci product recommendations for a product style code, or omit it to get trending items with names, prices, images, and stock.

Instructions

Gucci product recommendations. Returns one Gucci recommendations shelf: product summaries (name, price, image, stock) from either a given product's own "You May Also Like" carousel (style_code set) or the site's general trending-items shelf (style_code omitted). style_code comes from gucci-search's or gucci-category's own style_code field.

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum products to return, defaults to 10, maximum 20
style_codeNoProduct style code to get related items for; omit for the site's general trending-items shelf instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It helpfully discloses the return shape (name, price, image, stock) and confirms this is a read-only recommendation fetch, but says nothing about rate limits, auth, or pagination behavior. Adequate but with gaps.

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, zero waste, with the core purpose and the two modes front-loaded before the upstream-source detail. 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 2-parameter read tool with no annotations and no output schema, the description covers both the input semantics and the return fields, so an agent has what it needs. Minor omissions like max/default behavior are left to the schema.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the semantic switch on style_code (set = per-product carousel, omitted = site trending shelf) and where that code originates, adding genuine meaning over the raw parameter text.

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 ('Returns one Gucci recommendations shelf') and enumerates the return payload (name, price, image, stock), which distinguishes it from the sibling gucci_product, gucci_search, and gucci_suggest tools 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 routes between the two operating modes: set style_code for a product's 'You May Also Like' carousel, omit it for the general trending shelf, and names gucci-search/gucci-category as the source of style_code. It does not state when this tool is preferable to plain search, so it stops short of full 5-level guidance.

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