Skip to main content
Glama
Sign In
Vinted MCP and CLI Server

Vinted MCP and CLI Server

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_item

Fetch complete item details by Vinted item ID (with country) or by a direct Vinted item URL. Returns title, price, currency, brand, size, condition, full description, all photo URLs, creation date, item URL, favourite count, and seller…

Instructions

Fetch complete item details by Vinted item ID (with country) or by a direct Vinted item URL. Returns title, price, currency, brand, size, condition, full description, all photo URLs, creation date, item URL, favourite count, and seller username/ID. Automatically falls back to HTML scraping when the JSON API is unavailable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFull Vinted item URL, e.g. "https://www.vinted.fr/items/5678901234-nike-air-max". Country is inferred from the URL automatically.
itemIdNoNumeric Vinted item ID, e.g. 5678901234
countryNoCountry site (required when using itemId; inferred automatically when url is provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.3
    • removedInput schema / properties / browser
      Removed value: -{
-  "default": false,
-  "description": "Use headless browser for retrieval. Requires optional Playwright deps; only needed for items blocked by bot detection.",
-  "type": "boolean"
-}
  2. Changed4 schema fields changedv1.0.1
    • addedInput schema / properties / browser / description
      Added value: +"Use headless browser for retrieval. Requires optional Playwright deps; only needed for items blocked by bot detection."
    • addedInput schema / properties / country / description
      Added value: +"Country site (required when using itemId; inferred automatically when url is provided)"
    • addedInput schema / properties / itemId / description
      Added value: +"Numeric Vinted item ID, e.g. 5678901234"
    • addedInput schema / properties / url / description
      Added value: +"Full Vinted item URL, e.g. \"https://www.vinted.fr/items/5678901234-nike-air-max\". Country is inferred from the URL automatically."
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose a meaningful trait: automatic fallback to HTML scraping when the JSON API is unavailable, which sets reliability expectations. It omits rate-limit, error, and permission behavior, so not a full 5.

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: retrieval modes first, then return fields, then the scrape-fallback caveat. Every sentence earns its place with no redundancy.

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?

There is no output schema, so enumerating the returned fields (title, price, currency, brand, size, condition, description, photos, seller, etc.) is genuinely valuable. Combined with the input-mode and fallback notes, the definition is nearly complete; only failure/limit behavior is unaddressed.

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 three parameters are already documented in the schema, including the country-required-with-itemId rule. The description restates the two modes but adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 and resource ('Fetch complete item details') plus the two lookup modes (item ID with country, or direct URL), which cleanly separates it from search_items and compare_prices. An agent knows exactly what this returns without opening the schema.

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?

Gives clear invocation context: country is required with itemId but inferred from a URL, so the agent knows how to call either mode. It stops short of stating when to prefer this over siblings such as search_items or compare_prices (e.g., used to expand a search hit into full details).

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