Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vestiaire_product

Retrieve a Vestiaire Collective listing's public details from its URL: price, brand, category, condition, material, color, size, seller summary, and photos. Returns clean JSON data.

Instructions

Vestiaire Collective listing detail. Returns a single Vestiaire Collective listing's public detail: price, brand, category, condition, material, color, size, seller summary, and photos. path is the listing's URL or site-relative path, as returned by /vestiaire/search's url field -- the numeric id alone cannot be resolved to a page. Public data, sourced from Vestiaire Collective's own listing page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesListing URL or path, from a search result's url field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description must carry the full burden. It clearly states the tool is read-only (returns public detail), specifies the input as a URL/path, and mentions the source (Vestiaire Collective's own listing page). It also clarifies that the numeric ID alone is insufficient, providing a key behavioral constraint.

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?

The description is efficient, with no irrelevant information. It front-loads the purpose, lists the fields returned, and provides essential usage guidance in a compact manner.

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?

For a tool with a single parameter, no output schema, and no annotations, the description is complete enough. It covers what the tool returns, the input format, and the relationship to the search tool, making it easily usable by an agent.

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 description coverage is 100%, so the schema already documents the parameter. However, the description adds significant value by explaining that the path must come from a search result's url field and that numeric id won't work, which goes beyond the basic schema description.

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?

The description clearly states 'Returns a single Vestiaire Collective listing's public detail' and lists the specific fields returned (price, brand, category, condition, material, color, size, seller summary, photos). This distinguishes it from the general search tool.

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?

The description explicitly states the required input format: 'path is the listing's URL or site-relative path, as returned by /vestiaire/search's url field' and warns 'the numeric id alone cannot be resolved to a page.' It also clarifies the data is public, sourced from the listing page, providing clear context for when to use this tool.

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