Crawlora MCP

vestiaire_search

Read-only

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. Use vestiaire_search_sellers to search Vestiaire Collective sellers by name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vestiaire_search"
  }
}

Input Schema

Name	Required	Description
`q`	No	Keyword search text
`page`	No	Page number, starting at 1
`sort`	No	Sort order. Allowed values: relevance, price_asc, price_desc, recency. Documented values: relevance, price_asc, price_desc, recency.
`brand_id`	No	Brand id, from a prior search's facets.brands
`per_page`	No	Results per page, up to 60
`category_id`	No	Category id, from /vestiaire/categories
`condition_id`	No	Condition id. Allowed values: 1, 2, 3, 4, 5. Documented values: 1, 2, 3, 4, 5.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 7, 2026

addedInput schema / properties / brand_id / description

Added value: +"Brand id, from a prior search's facets.brands"

addedInput schema / properties / category_id / description

Added value: +"Category id, from /vestiaire/categories"

addedInput schema / properties / condition_id / description

Added value: +"Condition id. Allowed values: 1, 2, 3, 4, 5. Documented values: 1, 2, 3, 4, 5."

addedInput schema / properties / page / description
```
Added value: +"Page number, starting at 1"
```
addedInput schema / properties / per_page / description
```
Added value: +"Results per page, up to 60"
```
addedInput schema / properties / q / description
```
Added value: +"Keyword search text"
```

addedInput schema / properties / sort / description

Added value: +"Sort order. Allowed values: relevance, price_asc, price_desc, recency. Documented values: relevance, price_asc, price_desc, recency."

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the data is public and upstream-sourced, and there is a hard 1000-offset pagination ceiling with a prescribed workaround. It does not mention rate limiting or auth, but those are minor for a public read tool.

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?

Purpose is front-loaded in the first clause, followed by param value lists, id sourcing, the pagination constraint, and the sibling pointer. Every sentence is useful, though the sort-value and id-source lists partially restate what the schema already documents, adding mild redundancy.

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?

With an output schema present, the description need not explain return shapes. Purpose, filterable dimensions, id provenance, the pagination ceiling, and the sibling alternative are all covered, which is everything needed to invoke this correctly.

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 the baseline is 3, and the description adds meaning beyond it: it clarifies the valid sort ordering semantics, states where category_id/condition_id originate, and introduces the page*per_page <= 1000 interaction rule that the schema does not express. Solid value-add on top of a fully documented schema.

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') against a named resource ('Vestiaire Collective's public pre-owned luxury resale catalog') and enumerates the filterable facets (keyword, category, brand, condition). It distinguishes itself from vestiaire_search_sellers by naming that sibling explicitly, so an agent can route correctly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (vestiaire_search_sellers) and the condition that selects it, points to /vestiaire/categories and /vestiaire/conditions for id sourcing, and gives an explicit when-not rule: the 1000 offset ceiling means narrowing the query rather than paging deeper. Nothing about when to use this is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.