Vinted MCP and CLI Server

compare_prices

Compare prices for a search query across multiple Vinted country sites simultaneously. Returns median, mean, stdDev, min, max, and sample count per country along with the local currency.

Instructions

Compare prices for a search query across multiple Vinted country sites simultaneously. Returns median, mean, stdDev, min, max, and sample count per country along with the local currency. Supports the same brand/size/color/condition filters as search_items for precise cross-country comparisons. Useful for finding the cheapest market or understanding cross-border price gaps.

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": {
      "query": "<query>"
    },
    "name": "compare_prices"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Brand names; automatically resolved to IDs
`limit`	No	Number of listings to sample per country. Higher values give more accurate statistics (max 96).
`query`	Yes	Item to compare prices for, e.g. "Levi 501 jeans" or "iPhone 14 case"
`sizeIds`	No	Size IDs to filter by (from resolve_size_ids)
`brandIds`	No	Numeric brand IDs to filter by (from search_brands)
`colorIds`	No	Color IDs to filter by (from get_colors)
`condition`	No	Item condition filter
`countries`	No	List of country codes to compare. Defaults to ["fr","de","it","es","nl","pl"] if omitted.
`categoryId`	No	Category ID from get_categories

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.6.3Oct 13, 2026

addedInput schema / properties / brand

Added value: +{
+  "description": "Brand names; automatically resolved to IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / brandIds

Added value: +{
+  "description": "Numeric brand IDs to filter by (from search_brands)",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / categoryId

Added value: +{
+  "description": "Category ID from get_categories",
+  "type": "integer"
+}

addedInput schema / properties / colorIds

Added value: +{
+  "description": "Color IDs to filter by (from get_colors)",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / condition

Added value: +{
+  "description": "Item condition filter",
+  "items": {
+    "enum": [
+      "new_with_tags",
+      "new_without_tags",
+      "very_good",
+      "good",
+      "satisfactory"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / countries / description

Previous value: -"List of country codes to compare. Defaults to all 19 Vinted countries if omitted."New value: +"List of country codes to compare. Defaults to [\"fr\",\"de\",\"it\",\"es\",\"nl\",\"pl\"] if omitted."

addedInput schema / properties / sizeIds

Added value: +{
+  "description": "Size IDs to filter by (from resolve_size_ids)",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

Changed3 schema fields changedv1.0.1May 6, 2026

addedInput schema / properties / countries / description

Added value: +"List of country codes to compare. Defaults to all 19 Vinted countries if omitted."

addedInput schema / properties / limit / description

Added value: +"Number of listings to sample per country. Higher values give more accurate statistics (max 96)."

addedInput schema / properties / query / description

Added value: +"Item to compare prices for, e.g. \"Levi 501 jeans\" or \"iPhone 14 case\""

First observedv1.0.0May 6, 2026

TDQS

A3.9/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 disclosure burden. It helpfully enumerates the return shape (median, mean, stdDev, min, max, sample count, local currency), but says nothing about the cost profile of fanning out to as many as 19 countries or any rate/perf implications.

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

Conciseness4/5

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

Three front-loaded sentences with no filler; the core action and scope come first. There is mild redundancy between "precise cross-country comparisons" and "cross-border price gaps," which keeps it just short of a 5.

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?

For a 9-parameter tool with no output schema and no annotations, the description does solid work: it explains the aggregate return values, the filter parity with search_items, and the analytical purpose. Minor gaps remain around sampling cost and defaults, but an agent has enough to call it correctly.

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 all nine parameters are already documented in the schema, making 3 the baseline. The description adds a useful cross-reference (same filters as search_items) but no parameter-level syntax or format detail beyond that.

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 (compare), resource (prices), and scope (across multiple Vinted country sites simultaneously). An agent can immediately distinguish this from search_items, which surfaces listings rather than aggregate statistics.

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?

Explicitly frames the use case ("finding the cheapest market or understanding cross-border price gaps") and cross-references search_items for the shared filter set. It lacks an explicit when-not condition, but the context is clearly established.

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

Deploy Server