Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gucci_search

Search Gucci's product catalog. Searches Gucci's US product catalog by keyword using the storefront's public catalog. Results include card-level data and the live total count; per-product colors, materials, sizes, gender, and line are…

Instructions

Search Gucci's product catalog. Searches Gucci's US product catalog by keyword using the storefront's public catalog. Results include card-level data and the live total count; per-product colors, materials, sizes, gender, and line are omitted when the search source does not provide them. A genuinely empty result returns a well-formed empty products list. The response's size_facets field lists live size values and counts -- pass one as size on a follow-up call to filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keyword
pageNoOne-based page number, defaults to 1
sizeNoFilter to products listing this exact size as available. See size_facets for live values -- omit size to see all sizes first.
limitNoResults per page, defaults to 24, maximum 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / size / description
      Previous value: -"Filter to products listing this exact size as available (e.g. \\"New value: +"Filter to products listing this exact size as available. See size_facets for live values -- omit size to see all sizes first."
  2. Addedv1.17.5

TDQS

A4.1/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 burden and does so reasonably: it discloses US-only scope, that it uses the public storefront catalog, that some per-product attributes (colors, materials, sizes, gender, line) may be omitted, and that empty results return a well-formed empty list. It omits auth requirements, rate limits, and pagination behavior beyond the limit param.

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?

Information is front-loaded (purpose first, then result shape, then the size_facets workflow). Five sentences are mostly earned, though the card-level-data sentence and the empty-result sentence overlap slightly in coverage of return behavior.

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?

With no output schema, the description does the work of explaining return shape: card-level data, live total count, size_facets, and empty-result behavior. It is largely complete for a search tool, missing only operational details like auth and pagination limits.

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%, so all four parameters are already documented in the schema. The description reinforces the size/size_facets relationship, but that is largely a restatement of the size param's own schema description, so baseline 3 is appropriate.

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 (Gucci's product catalog) with keyword scope and the US storefront constraint. An agent can distinguish it from gucci_product, gucci_categories, and gucci_suggest without opening a 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?

Provides clear context for how to use results: consult size_facets and pass a value as size on a follow-up call. It does not name sibling tools or state when to prefer gucci_product or gucci_category instead, so it stops short of explicit alternatives.

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