Vinted MCP and CLI Server

search_all_items

Search Vinted listings and automatically paginate through all results, returning up to maxItems items in a single call. Use this instead of search_items when you need comprehensive results — e.g.

Instructions

Search Vinted listings and automatically paginate through all results, returning up to maxItems items in a single call. Use this instead of search_items when you need comprehensive results — e.g. "find all Nike shoes under €30" or "list every item in size M from this brand". Pages are fetched concurrently for speed. Returns the same item fields as search_items.

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": "search_all_items"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	Size labels to filter by, e.g. ["M", "L"]. Automatically resolved to IDs.
`brand`	No	Brand names; automatically resolved to IDs
`color`	No	Color names to filter by, e.g. ["black", "white"]. Automatically resolved to IDs.
`query`	Yes	Search keywords
`sortBy`	No	Sort order
`country`	No	Vinted country site to search	fr
`sizeIds`	No	Numeric size IDs. Prefer size[] for label-based lookup.
`brandIds`	No	Numeric brand IDs from search_brands
`colorIds`	No	Numeric color IDs. Prefer color[] for name-based lookup.
`maxItems`	No	Maximum total items to collect across all pages (default 200, max 1000)
`maxPages`	No	Maximum number of pages to fetch regardless of maxItems
`priceMax`	No	Maximum price in local currency
`priceMin`	No	Minimum price in local currency
`condition`	No	Item condition filter
`categoryId`	No	Category ID from get_categories

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.6.3Oct 13, 2026

addedInput schema / properties / color

Added value: +{
+  "description": "Color names to filter by, e.g. [\"black\", \"white\"]. Automatically resolved to IDs.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / colorIds / description

Previous value: -"Color IDs to filter by. Use get_colors to discover all available color IDs."New value: +"Numeric color IDs. Prefer color[] for name-based lookup."

addedInput schema / properties / size

Added value: +{
+  "description": "Size labels to filter by, e.g. [\"M\", \"L\"]. Automatically resolved to IDs.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / sizeIds / description

Previous value: -"Size IDs to filter by"New value: +"Numeric size IDs. Prefer size[] for label-based lookup."

Changed1 schema field changedv1.0.2May 6, 2026

addedInput schema / properties / colorIds

Added value: +{
+  "description": "Color IDs to filter by. Use get_colors to discover all available color IDs.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

Addedv1.0.1May 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful beyond-schema behavior: it paginates automatically, fetches pages concurrently for speed, and returns the same item fields as search_items. It does not cover failure modes, rate limits, or auth, which is a modest gap for a read-only tool.

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?

Three tight sentences, front-loaded with what the tool does, then the routing rule with examples, then the concurrency note. Every sentence earns its place with no filler.

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?

Covers the essentials for a 15-parameter paginating search tool: pagination semantics, the maxItems bound, and field parity with search_items stand in for a missing output schema. Missing only operational caveats (errors, rate limits) that a heavy auto-paginating tool with no annotations arguably warrants.

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 15 parameters are already documented. The description only restates the maxItems ceiling behavior, adding little beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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+resource (search Vinted listings) and the defining behavior (auto-paginate all results up to maxItems). It explicitly names and differentiates itself from the sibling search_items, so an agent can choose between them without inspecting 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?

Gives an explicit routing rule — 'Use this instead of search_items when you need comprehensive results' — plus concrete examples ('find all Nike shoes under €30', 'list every item in size M from this brand'). The alternative and the condition that selects it are both named.

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

Deploy Server