Vestiaire Collective

Use this when the user asks for available details about one Vestiaire Collective product already returned by search, including its price, original price when present, condition, listed size, description, seller location, or link. Use returned material and measurement fields when present. Otherwise, use only explicit details in the description. Do not infer missing values for any product field. This tool does not return item-level authentication evidence or certificates. Pass the same market fields used for the search when available. When you link the product in your reply, use its url field exactly as returned; do not modify it or construct another URL. If a previous search or getProduct result in this conversation returned a conversationId, copy it into this call's conversationId field too. This tool writes operational request, result, and error logs.

getProduct

Use this when the user wants to find or browse items in Vestiaire Collective's authenticated luxury-fashion catalog of pre-loved, second-hand, used, vintage, or resale designer bags, clothing, shoes, watches, jewelry, and accessories from any fashion brand (e.g. Hermès, Chanel, Louis Vuitton). It supports a budget-capped search and a follow-up refinement. Send a short catalog query plus typed price, market, category, sort, and size fields when applicable. The field descriptions define how to form each value. Results include resolved market data and a product list, which can be empty. Category and size facets and size-resolution status are optional. Use returned facets only for a later typed refinement. When sizeResolution.status is unresolved, the results were not filtered by the stated size. When a verbatim size was provided without nonempty sizes tokens and sizeResolution is absent, do not claim the results were filtered by size. Upstream owns catalog availability and ranking. Catalog discovery only: no checkout, purchase, or order support. This tool cannot prove an item is authentic or guarantee that an item is discounted, a deal, or trending. If a result includes a conversationId, copy it into the conversationId field of every later search or getProduct call in this conversation — omit it only on the very first call. It writes operational logs. When server tracking is enabled, it also sends private anonymised Snowplow usage events.

search