Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vinted_category

Fetch Vinted listings for a specific category by ID, with optional price range and sort order to browse relevant items.

Instructions

Vinted listings for a category. Returns Vinted listings for a specific category, 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 category page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric Vinted category ID, from a /vinted/item result's categories breadcrumb 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

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the data is public (no auth needed) and 'sourced from Vinted's own server-rendered category page', hinting at HTML-scraping behavior. But it does not disclose pagination behavior, response shape, rate limits, or behavior on invalid category IDs, which matters for a tool with a page parameter and no 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.

Conciseness3/5

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

The description is short and front-loaded with the core function, and the 'Public data, sourced from...' sentence earns its place. However, it contains redundancy: the opening fragment 'Vinted listings for a category' merely restates the tool name, and the full order enum is duplicated verbatim from the schema. Four sentences with this level of repetition is slightly wasteful.

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?

For a 5-parameter listing tool with no annotations and no output schema, the description covers the essential purpose, filter options, sort values, and data source. Gaps remain: it never describes what the returned listings look like (no output schema to fall back on), how page pagination behaves, or what happens with an invalid category ID. Adequate for basic use but not fully 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 schema already documents all five parameters adequately, including the order enum values. The description mostly restates the schema content ('optional price filtering and sort order', the order enum list) without adding new meaning, and it adds no format or interaction details beyond the schema.

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 states a clear verb ('Returns') and resource ('Vinted listings for a specific category'), and scopes the tool away from the sibling vinted_categories by emphasizing 'specific category'. It also enumerates the optional filtering and sort dimensions. It doesn't explicitly name sibling alternatives, which keeps it from a 5.

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 context is implied rather than explicit: the description signals this is for fetching listings within one category with price/order filters. The id parameter's provenance hint ('from a /vinted/item result's categories breadcrumb link') is genuinely useful guidance for sourcing the required argument. However, there is no explicit when-to-use/when-not-to-use guidance or comparison against siblings like 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.

Deploy Server

Other Tools