Crawlora MCP

vinted_catalog

Read-only

Search Vinted resale listings by text, optional price range, and sort, returning listing summaries with condition and favorites. Use vinted_item for a listing or vinted_brands to discover brands.

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": {
      "search_text": "<search_text>"
    },
    "name": "vinted_catalog"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1
`order`	No	Sort order. Allowed values: relevance, newest_first, price_high_to_low, price_low_to_high. Documented values: relevance, newest_first, price_high_to_low, price_low_to_high.
`price_to`	No	Maximum price
`price_from`	No	Minimum price
`search_text`	Yes	Search text

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.

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / order / description

Added value: +"Sort order. Allowed values: relevance, newest_first, price_high_to_low, price_low_to_high. Documented values: relevance, newest_first, price_high_to_low, price_low_to_high."

addedInput schema / properties / page / description
```
Added value: +"Page number, starting at 1"
```
addedInput schema / properties / price_from / description
```
Added value: +"Minimum price"
```
addedInput schema / properties / price_to / description
```
Added value: +"Maximum price"
```
addedInput schema / properties / search_text / description
```
Added value: +"Search text"
```

First observedOct 5, 2026

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, so the safety and openness profile is covered. The description adds that results are listing summaries containing condition and favorites, which is useful, but says nothing about pagination behavior or rate limits.

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 waste, and the core search purpose plus its filters are front-loaded before the routing hint. 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?

With an output schema documenting return values and annotations covering safety, the description only needs to state scope and routing, which it does. It could add a note on pagination or result volume, but nothing essential for calling the tool is missing.

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 description coverage is 100%, so the schema already documents all five parameters including the order enum and page/price bounds. The description restates text, price range, and sort but adds no 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?

States a specific verb (Search) and resource (Vinted resale listings) plus the filter facets (text, price range, sort) and return shape (listing summaries with condition and favorites). It names two sibling tools so an agent can distinguish this catalog search from vinted_item and vinted_brands.

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?

Explicitly routes the agent: use vinted_item for a single listing and vinted_brands to discover brands, which clarifies this tool's search role. It gives clear context and alternatives, though it does not state when to prefer catalog search over e.g. category browse.

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?