Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

quince_search

Search or browse Quince's product catalog by keyword, department, category, material, color, size, or price range; filters combine to narrow results.

Instructions

Search or browse Quince products. Searches or browses Quince's (quince.com) product catalog. q, department, category, material, color, size, min_price, and max_price are all optional and combine as an AND -- unlike some other families' search/category-browse split, a free-text q can be combined with any of the facet filters in the same request, or every field can be omitted to browse the full catalog by Quince's own relevance/popularity ranking. department accepts one of the values quince-categories' own business_departments[].value field returns (for example Women, Men, Kids & Baby, Home, CPG, Emerging); category, material, color, and size similarly accept values from quince-categories' own categories[].value/materials[].value/colors[].value/sizes[].value fields (or quince-navigation's own browsable category/subcategory slugs for a curated, hierarchical alternative to the flat category facet). Keyword search uses typo-tolerant relevance ranking, not a guaranteed exact match. A query with genuinely zero matches (for example a nonsense string) returns a well-formed empty result rather than an error.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search query
pageNoOne-based page number, defaults to 1
sizeNoSize facet filter, from quince-categories' own sizes[].value field
colorNoPrimary color facet filter, from quince-categories' own colors[].value field
limitNoResults per page, defaults to 24, maximum 100
categoryNoCategory facet filter, from quince-categories' own categories[].value field
materialNoMaterial facet filter, from quince-categories' own materials[].value field
max_priceNoMaximum price (inclusive), in USD
min_priceNoMinimum price (inclusive), in USD
departmentNoBusiness department facet filter, from quince-categories' own business_departments[].value field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

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 burden, and it does meaningful work: keyword search is typo-tolerant relevance ranking rather than exact match, and a zero-match query returns a well-formed empty result instead of an error. It omits auth/rate-limit and return-shape context, but the matching behavior is a genuine disclosure beyond structured fields.

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 purpose and dense with useful constraints, but the opening two sentences (

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, no-annotation, no-output-schema tool, the description covers matching behavior, facet sources, and empty-result handling well, so an agent can call it correctly. However it never addresses pagination semantics beyond defaults, ranking caveats across pages, or any return-shape expectations, which are the remaining gaps for a search tool.

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 baseline is 3, but the description adds real value: it enumerates which fields are optional, states they combine as AND, and gives concrete example department values (Women, Men, Kids & Baby, Home, CPG, Emerging). The facet-source references largely repeat the schema, keeping this from a 5.

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 (search/browse Quince's product catalog at quince.com) and immediately differentiates itself from the family's search/browse split by explaining that q and facets combine in one request. An agent can distinguish this from quince_categories, quince_navigation, and quince_product 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?

Explains when to search (q combined with facets) versus browse (omit all fields to use Quince's own ranking), and points to quince-navigation as the curated hierarchical alternative for category browsing. It does not explicitly route to siblings like quince_product for a single-item lookup, so it stops short of full when/when-not 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