Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vinted_brand

Fetch Vinted listings for a specific brand, with optional minimum and maximum price filters and sort order. Use a brand ID from an item result to browse public server-rendered 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / order / enum
      Added value: +[
+  "relevance",
+  "newest_first",
+  "price_high_to_low",
+  "price_low_to_high"
+]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that data is public and sourced from Vinted's server-rendered brand page, which is useful context. However, it does not mention pagination, rate limits, or response format, and it repeats the enum values already present in the 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?

The description is two sentences, front-loaded with the purpose, then adds sort values and data source. Every sentence earns its place; there is no redundancy or fluff. It is highly concise and well-structured.

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?

Given there is no output schema and no annotations, the description should cover response expectations and usage constraints. It mentions price filtering and sort order, but does not explain what the returned listings look like, pagination behavior, or any limits. The schema covers parameters, but the lack of response format is a gap. It is adequate but not complete.

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 price filtering and sort order, but these are already documented in the schema. It adds no new meaning beyond what the schema provides, so it does not exceed the baseline.

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?

The description clearly states it returns Vinted listings for a specific brand, with optional price filtering and sort order. It is specific about the resource and action, but it does not explicitly differentiate from sibling tools like vinted_catalog or vinted_brands, though the singular 'brand' implies specificity.

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?

The description implies when to use it (for listings of a specific brand) but does not explicitly state alternatives or when not to use it. There is no guidance on when to prefer this over vinted_catalog or vinted_category. The context is clear enough, but exclusions are absent.

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

Deploy Server

Other Tools