Crawlora MCP

vinted_brand

Read-only

Fetch Vinted listing rows for one brand, with optional price filters and sort order. Use vinted_brands to discover accepted brand names or vinted_item for one known listing.

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

Input Schema

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

TDQS

A4.2/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 safe read-only, public-web profile is covered. The description adds only that it fetches listing rows with optional filters and sort order—details already present in the schema—without disclosing pagination behavior, rate limits, or output shape beyond the output schema.

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 with zero waste; purpose and scope are front-loaded, and the alternative-tool guidance follows immediately. 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 present and annotations covering safety, the description need not explain return values. It covers purpose and alternatives for this simple listing-fetch tool, though it could more explicitly connect vinted_brands discovery to the numeric brand ID required by the id parameter.

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_to, and price_from are already documented. The description mentions optional price filters and sort order but adds no format, default, or enum semantics 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.

Purpose5/5

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

States a specific verb 'Fetch' and resource 'Vinted listing rows', scoped to one brand with optional price filters and sort order. It explicitly differentiates from vinted_brands (discovery) and vinted_item (single listing), so an agent can identify it 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?

Provides explicit routing: use vinted_brands to discover accepted brand names and vinted_item for one known listing. The scope 'for one brand' clarifies when this tool applies versus broader catalog/search siblings, leaving little inference.

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.