Crawlora MCP

vinted_item

Read-only

Fetch one public Vinted listing detail record, including condition, size, price, and photos. Use vinted_catalog to browse listings or vinted_member for a seller's public 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": "vinted_item"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric Vinted item ID, from a /vinted/catalog result's id field

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.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / id / description
```
Added value: +"Numeric Vinted item ID, from a /vinted/catalog result's id field"
```
First observedOct 5, 2026

TDQS

A4.3/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, so the safety profile is covered structurally. The description adds only that the listing is public data and enumerates the main fields; it says nothing about auth, rate limits, or listing-lifecycle caveats. Adequate but not rich beyond what annotations provide.

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, no filler, with the core fetch purpose front-loaded and the alternative routing trailing. Nothing repeats the name or title.

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 single-item detail tool with an output schema carrying the return shape, one fully documented parameter, and annotations covering safety/openness, the description supplies everything needed: purpose, field scope, and sibling routing. No relevant gap remains.

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% and the single required `id` is documented in the schema as a numeric Vinted item ID sourced from a /vinted/catalog result. The description adds no further syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ("Fetch one public Vinted listing detail record") with the returned fields itemized (condition, size, price, photos). It explicitly names the siblings it is not (vinted_catalog for browsing, vinted_member for seller profiles), so an agent can separate it from them without opening schemas.

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?

It states the retrieval context (look up a single listing by id) and routes the agent to explicit alternatives with their own conditions ("Use vinted_catalog to browse listings or vinted_member for a seller's public profile"). The when-to-use-this vs when-to-use-that split is fully spelled out.

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.

Resources

Need Help?