Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gucci_category

Retrieve products from a Gucci category listing, including names, prices, colors, images, stock, and page metadata, using a category path and optional page accumulation.

Instructions

Browse a Gucci category listing. Returns one Gucci category/browse listing: products (name, price, colors, images, stock) plus the upstream's own product count, page count, sibling-category counts, and sort options. category comes from gucci-categories' own category field. page selects how many of the upstream's own batches to accumulate -- Gucci's own category pages page this way: requesting page=N returns every product from page 1 through page N combined (its own "Load All" button simply requests the last page), not a single page's worth. Defaults to 1 (the upstream's own first batch, 36 products); request page equal to the response's own pages_count to fetch a category's complete listing in one call.

Input Schema

NameRequiredDescriptionDefault
pageNoHow many of the upstream's own batches to accumulate, defaults to 1 (see description)
categoryYesCategory path from gucci-categories' own category field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 well on the non-obvious point: page=N accumulates batches 1..N rather than returning a single page, with the default (1, ~36 products) and the pages_count shortcut spelled out. It omits any auth, rate-limit, or error-behavior context, which is why it is not a 5.

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?

Front-loaded with the purpose, then the return shape, then parameter semantics in a logical order. The pagination explanation is somewhat repetitive ('upstream's own batches', 'Gucci's own category pages page this way') but every sentence carries information an agent needs.

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 2-param tool with no annotations and no output schema, the description covers everything needed: what it returns, where category comes from, and the counter-intuitive pagination behavior with a concrete shortcut for a full fetch. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), and the description substantially exceeds the schema: it explains the actual accumulation semantics of 'page', the meaning of its default, and where 'category' is sourced from. The schema's own page description even defers to the description, so this is load-bearing parameter context.

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 ('Browse') and resource ('Gucci category listing') and immediately scopes what it returns (products plus counts and sort options). It also distinguishes itself from the sibling gucci_categories by naming that tool as the source of the category value.

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?

It gives clear context for use: category must come from gucci-categories' own category field, and it explains how to fetch a complete listing. It does not, however, explicitly exclude or contrast with gucci_search or gucci_product, so the agent must infer when a category browse is preferable to a search.

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