Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

vestiaire_search

Search Vestiaire Collective's pre-owned luxury resale catalog by keyword, brand, category, condition, and sort order. Retrieve paginated listings for resale research.

Instructions

Vestiaire Collective listing search. Searches Vestiaire Collective's public pre-owned luxury resale catalog by keyword, category, brand, and condition, with sort and pagination. sort values: relevance, price_asc, price_desc, recency. category_id and condition_id come from /vestiaire/categories and /vestiaire/conditions. page * per_page cannot exceed an offset of 1000 (the upstream service's own pagination limit) -- narrow the query instead of paging deeper. Public data, sourced from Vestiaire Collective's own search service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeyword search text
pageNoPage number, starting at 1
sortNoSort order. Allowed values: relevance, price_asc, price_desc, recency
brand_idNoBrand id, from a prior search's facets.brands
per_pageNoResults per page, up to 60
category_idNoCategory id, from /vestiaire/categories
condition_idNoCondition id. Allowed values: 1, 2, 3, 4, 5

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?

No annotations are supplied, so the description carries the full burden. It discloses that the data is public and sourced from Vestiaire Collective's own search service, implying a read-only operation, and reveals the upstream pagination limit. It does not discuss rate limits or auth, but for a public search this is adequate.

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?

Three sentences, front-loaded with the primary purpose, then precise parameter-source references and a critical constraint. No filler; every sentence earns its place.

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?

Covers what is searched, all filter dimensions, sort options, parameter provenance, and a key pagination restriction. With no output schema, the description adequately prepares an agent to construct a valid query. Nothing essential is missing.

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. The description adds value by tying category_id and condition_id to specific sibling endpoint sources and by documenting the page*per_page offset limit that the schema does not mention. This goes beyond the bare parameter definitions.

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 ('searches'), a precise resource ('Vestiaire Collective's public pre-owned luxury resale catalog'), and the scope (by keyword, category, brand, condition). Clearly differentiates from sibling tools like vestiaire_product or vestiaire_search_sellers by calling it a 'listing search'.

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 concrete guidance: where to source category_id and condition_id (from /vestiaire/categories and /vestiaire/conditions) and a hard pagination constraint with advice to narrow the query rather than page deeper. However, it does not explicitly name alternative search tools or state when not to use this one.

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