Skip to main content
Glama
googlarz

Vinted MCP and CLI Server

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_items

Search Vinted second-hand listings across 19 countries with rich filters for price, brand, category, size, color, and condition. Returns paginated results with item details.

Instructions

Search Vinted second-hand listings with rich filters across 19 country sites. Returns a paginated list of items — each with title, price, currency, brand, size, condition, photo URL, item URL, favourite count, and seller info. Use get_categories to discover valid categoryId values and search_brands to resolve brand names to IDs. For comprehensive multi-page results use search_all_items instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number starting at 1
brandNoBrand names to filter by, e.g. ["Nike", "Adidas"]. Automatically resolved to IDs via search_brands.
queryYesSearch keywords, e.g. "Nike Air Max 90" or "levi 501 jeans"
dateToNoReturn items listed on or before this date. ISO-8601 format, e.g. "2024-12-31"
sortByNoSort order for results. Defaults to relevance.
countryNoVinted country site to search (fr, de, uk, pl, es, nl, be, it, pt, cz, sk, hu, ro, lt, lv, ee, fi, at, se)fr
perPageNoResults per page, 1–96. Defaults to 20.
sizeIdsNoSize IDs to filter by. Discover valid IDs by inspecting results from a previous search in the same category, or use get_size_groups to browse all size groups.
brandIdsNoNumeric Vinted brand IDs from search_brands. Prefer the brand[] parameter for name-based lookup.
colorIdsNoColor IDs to filter by (e.g. [1] for black, [3] for white). Use get_colors to discover all available color IDs and their names.
dateFromNoReturn items listed on or after this date. ISO-8601 format, e.g. "2024-01-01"
priceMaxNoMaximum price in the local currency of the selected country
priceMinNoMinimum price in the local currency of the selected country
conditionNoItem condition filter; multiple values are OR-ed together
categoryIdNoCategory ID from get_categories (e.g. 4 = women's clothing, 5 = men's clothing, 1231 = women's shoes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • addedInput schema / properties / colorIds
      Added value: +{
+  "description": "Color IDs to filter by (e.g. [1] for black, [3] for white). Use get_colors to discover all available color IDs and their names.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / sizeIds / description
      Previous value: -"Size IDs to filter by. Discover valid IDs by inspecting results from a previous search in the same category."New value: +"Size IDs to filter by. Discover valid IDs by inspecting results from a previous search in the same category, or use get_size_groups to browse all size groups."
  2. Changed14 schema fields changedv1.0.1
    • changedInput schema / properties / brand / description
      Previous value: -"Brand names; resolved to IDs via Vinted lookup"New value: +"Brand names to filter by, e.g. [\"Nike\", \"Adidas\"]. Automatically resolved to IDs via search_brands."
    • addedInput schema / properties / brandIds / description
      Added value: +"Numeric Vinted brand IDs from search_brands. Prefer the brand[] parameter for name-based lookup."
    • addedInput schema / properties / categoryId / description
      Added value: +"Category ID from get_categories (e.g. 4 = women's clothing, 5 = men's clothing, 1231 = women's shoes)"
    • addedInput schema / properties / condition / description
      Added value: +"Item condition filter; multiple values are OR-ed together"
    • addedInput schema / properties / country / description
      Added value: +"Vinted country site to search (fr, de, uk, pl, es, nl, be, it, pt, cz, sk, hu, ro, lt, lv, ee, fi, at, se)"
    • changedInput schema / properties / dateFrom / description
      Previous value: -"ISO date string e.g. 2024-01-01"New value: +"Return items listed on or after this date. ISO-8601 format, e.g. \"2024-01-01\""
    • addedInput schema / properties / dateTo / description
      Added value: +"Return items listed on or before this date. ISO-8601 format, e.g. \"2024-12-31\""
    • addedInput schema / properties / page / description
      Added value: +"Page number starting at 1"
    • addedInput schema / properties / perPage / description
      Added value: +"Results per page, 1–96. Defaults to 20."
    • addedInput schema / properties / priceMax / description
      Added value: +"Maximum price in the local currency of the selected country"
    • addedInput schema / properties / priceMin / description
      Added value: +"Minimum price in the local currency of the selected country"
    • addedInput schema / properties / query / description
      Added value: +"Search keywords, e.g. \"Nike Air Max 90\" or \"levi 501 jeans\""
    • changedInput schema / properties / sizeIds / description
      Previous value: -"Size IDs (use get_categories + search_items to discover)"New value: +"Size IDs to filter by. Discover valid IDs by inspecting results from a previous search in the same category."
    • addedInput schema / properties / sortBy / description
      Added value: +"Sort order for results. Defaults to relevance."
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details the return fields (title, price, etc.) and mentions pagination and 19 country sites. Could improve by noting authentication or rate limits, but overall sufficiently transparent.

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 sentences: first states purpose, second details return fields, third provides usage guidance. Front-loaded and no unnecessary words.

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?

With 15 params and no output schema or annotations, description covers core behavior, return structure, and related tools. Missing mention of authentication, but sufficient for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds value by explaining how to get category IDs (get_categories), brand resolution (search_brands), and size IDs (get_size_groups), going beyond schema descriptions.

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 'Search Vinted second-hand listings with rich filters across 19 country sites', specifying the verb 'search' and resource 'listings'. It distinguishes itself from sibling tools like search_all_items and get_item.

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?

Explicitly advises using get_categories for category IDs and search_brands for brand IDs, and directly says to use search_all_items for comprehensive multi-page results, providing clear when-to-use and alternatives.

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