Crawlora MCP

vinted_category

Read-only

Returns Vinted listings for a specific category, with optional price filtering and sort order. A category with no matching listings returns 404 rather than an empty

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_category"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Numeric Vinted category ID, from a /vinted/item result's categories breadcrumb link
`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

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 / id / description

Added value: +"Numeric Vinted category ID, from a /vinted/item result's categories breadcrumb link"

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"
```

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a genuinely useful behavioral quirk not in annotations: a category with no matches returns 404 rather than an empty result, which changes how an agent should interpret a failure.

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, purpose front-loaded, and the error-behavior caveat placed immediately after. 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 annotations and an output schema already present, the description only needs to state purpose, scope, and any non-obvious behavior — it does all three. Return format and pagination semantics are left to the output schema, which is reasonable.

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 id, page, order, price_from, and price_to are already documented. The description only gestures at 'price filtering and sort order' without adding format or syntax beyond what the schema provides; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (returns) and resource (Vinted listings scoped to a category) plus the optional facets (price, sort). It's clear what the tool does, though it does not name or differentiate itself from close siblings like vinted_brand or vinted_catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'for a specific category' — an agent can infer this is the category-browse variant. But there is no explicit when-to-use-vs-alternatives guidance distinguishing it from vinted_brand, vinted_catalog, or vinted_categories.

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?