Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

quince_product

Fetch complete Quince item details by handle, including title, description, review summary, color and size options, variant prices, stock status, and SKU.

Instructions

Get a Quince product. Returns product-detail data for one Quince product: title, description, review summary, every selectable option (color swatches with hex codes, sizes), and every color/size variant with its own price, original ("traditional retail") price, stock status, and SKU. handle is the product's URL path on quince.com (for example women/cashmere/cashmere-crewneck-sweater), returned by quince-search's own products[].handle field.

Input Schema

NameRequiredDescriptionDefault
handleYesProduct URL handle, from a search result's products[].handle field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden; it does so by richly disclosing the read payload, including that each variant carries its own price, original retail price, stock status, and SKU. It does not mention error behavior for an invalid handle or auth/rate-limit traits, so it falls short of a full disclosure.

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 core action ('Get a Quince product') followed by a dense but purposeful enumeration of the return payload and a handle-origin sentence. No filler, though the long single sentence listing fields is slightly heavy to parse.

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 must explain the return shape and does so thoroughly, and the single required parameter is fully covered. It stops short of pointing to the related review/FAQ siblings, but for a one-param detail endpoint it is essentially complete.

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?

With a single parameter at 100% schema coverage the baseline is 3, but the description adds real meaning: handle is the product's URL path on quince.com, gives a concrete example path, and explains where the value originates (search results). This goes beyond the schema's 'Product URL handle' phrasing.

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 ('Get a Quince product') and immediately enumerates the returned payload (title, options, variants, per-variant price/stock/SKU), which distinguishes it from the sibling quince_search that returns a list. An agent can tell what this returns without opening anything else.

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 establishes the workflow context by tying handle to 'quince-search's own products[].handle field', implying this is the detail step after a search. However, it never explicitly names alternatives (e.g., quince_product_reviews, quince_product_faq) or states when not to use it, so guidance is clear but not complete.

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