Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

vinted_brand

Search Vinted listings by brand ID, filter by price range, and sort results by relevance, newest, or price. Retrieve clean public data from Vinted's brand pages.

Instructions

Vinted listings for a brand. Returns Vinted listings for a specific brand, with optional price filtering and sort order. order values: relevance, newest_first, price_high_to_low, price_low_to_high. Public data, sourced from Vinted's own server-rendered brand page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric Vinted brand ID, from a /vinted/item result's brand link
pageNoPage number, starting at 1
orderNoSort order. Allowed values: relevance, newest_first, price_high_to_low, price_low_to_high
price_toNoMaximum price
price_fromNoMinimum price
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses 'Public data, sourced from Vinted's own server-rendered brand page', implying a read-only, no-auth operation. However, it does not mention pagination behavior, rate limits, or what fields a listing contains, which would be valuable context for a scraper tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes a redundant first sentence ('Vinted listings for a brand.') that repeats the second sentence. The order values are also listed in both the description and the schema, creating duplication. It is short but contains unnecessary waste.

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

Completeness3/5

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

There is no output schema, so the description should explain what a 'listing' looks like, but it only says 'returns Vinted listings' without describing the structure. It also lacks pagination details despite having a page parameter. Acceptable for a simple read tool, but significant gaps remain.

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 baseline is 3. The description mentions optional price filtering and sort order, but this information is already present in the schema's property descriptions. It adds no new meaning beyond what the schema provides.

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?

The description clearly states 'Returns Vinted listings for a specific brand', giving a specific verb (returns), resource (Vinted listings), and scope (specific brand). This distinguishes it from siblings like vinted_brands (list of brands) and vinted_item (single item).

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 description provides clear context: the tool is for a specific brand and supports optional price filtering and sort order. However, it does not explicitly mention alternatives or when not to use this tool compared to other Vinted tools like vinted_catalog or vinted_category. No exclusions are stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server