Skip to main content
Glama
googlarz

Vinted MCP and CLI Server

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_all_items

Retrieve all Vinted listings matching your search criteria by automatically fetching all pages of results. Supports filters for price, brand, size, color, and condition.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoBrand names; automatically resolved to IDs
queryYesSearch keywords
sortByNoSort order
countryNoVinted country site to searchfr
sizeIdsNoSize IDs to filter by
brandIdsNoNumeric brand IDs from search_brands
colorIdsNoColor IDs to filter by. Use get_colors to discover all available color IDs.
maxItemsNoMaximum total items to collect across all pages (default 200, max 1000)
maxPagesNoMaximum number of pages to fetch regardless of maxItems
priceMaxNoMaximum price in local currency
priceMinNoMinimum price in local currency
conditionNoItem condition filter
categoryIdNoCategory ID from get_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • 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"
+}
  2. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, but description discloses concurrency ('Pages are fetched concurrently for speed'), pagination behavior, and return field compatibility. Does not mention rate limits or error handling, but key behaviors are covered.

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?

Highly concise: two sentences cover purpose, usage, behavior, and output. Every sentence adds value with no wasted 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?

13 parameters all documented in schema; description adds pagination, concurrency, and output reference. Could mention limit behavior but overall sufficient for agent to use effectively.

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 each parameter has its own description. The tool description does not add significant new meaning beyond the schema; baseline 3 is appropriate.

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?

Clear verb and resource: 'Search Vinted listings' with automatic pagination. Explicitly distinguishes from sibling 'search_items' by stating use case for comprehensive results.

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 states when to use ('instead of search_items when you need comprehensive results') with concrete examples. Lacks explicit 'when not to use' but the guidance is clear for the intended scenario.

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