Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vestiaire_seller

Read-only

Fetch a Vestiaire Collective seller's public storefront profile and aggregate sales and follower counts by username. Use vestiaire_search_sellers to discover sellers before retrieving a profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesSeller id

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Seller id"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, matching the read-only 'Fetch' wording, so there is no contradiction. The description adds that the data is a public storefront plus aggregate counts, which is useful context, but it says nothing about auth, rate limits, or missing-seller behavior; with annotations carrying the safety profile and an output schema present, a 3 is appropriate.

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?

Two sentences, zero filler, with the primary action front-loaded before the routing advice. Every clause earns its place.

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

Completeness4/5

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

Given an output schema, read-only/open-world annotations, and a single documented parameter, the description covers what is needed to select and call the tool correctly, including the sibling to use first. It stops just short of clarifying whether the id is a username or a numeric seller id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% on a single required 'id' parameter described as 'Seller id', so the schema carries the load and the baseline is 3. The description's phrase 'by username' adds a hint about the identifier's nature, but it sits in mild tension with the schema's 'Seller id' wording rather than resolving it.

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 ('Fetch a Vestiaire Collective seller's public storefront profile') and enumerates what comes back ('aggregate sales and follower counts'). It names the sibling (vestiaire_search_sellers), so an agent can distinguish it from the discovery tool without opening either 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?

The second sentence gives explicit routing: use vestiaire_search_sellers to discover sellers first, then retrieve a profile. That names the alternative and the selecting condition, but there is no statement of when-not to use this tool or what input the id must be.

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

All Crawlora MCP toolsInspect
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.

Resources