Skip to main content
Glama
googlarz

Vinted MCP and CLI Server

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trending

Fetch the newest and trending items on Vinted for a specific country. Optionally filter by category to discover current popular items and new arrivals.

Instructions

Fetch the newest and trending items on Vinted for a given country, ordered by recency. Optionally scoped to a specific category. Useful for discovering what's currently popular, monitoring new arrivals, or finding deals as they are listed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of trending items to return, 1–96
countryNoVinted country site to fetch trending items fromfr
categoryIdNoOptional category ID from get_categories to restrict results to a specific department

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • addedInput schema / properties / categoryId / description
      Added value: +"Optional category ID from get_categories to restrict results to a specific department"
    • addedInput schema / properties / country / description
      Added value: +"Vinted country site to fetch trending items from"
    • addedInput schema / properties / limit / description
      Added value: +"Number of trending items to return, 1–96"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description must disclose behavior. It correctly describes the fetch as read-only and ordered by recency, but lacks details on authentication, rate limits, or pagination. This is adequate but minimal.

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?

Two sentences with no wasted words. The first sentence states the core action and constraints; the second provides usage guidance. Efficient and well-structured.

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?

The description covers the main purpose and usage scenarios. Missing details about pagination behavior or result format are minor; the limit parameter and ordering are mentioned. With no output schema, the description is reasonably complete for a simple list tool.

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 the baseline is 3. The description adds that scope is optional and items are ordered by recency, but these are already implied by schema descriptions. No additional value beyond schema.

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 it fetches the newest and trending items on Vinted for a given country, ordered by recency, with optional category scoping. This distinguishes it from sibling tools like search_items (general search) and get_seller_items (specific seller's items).

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?

The description provides clear usage context: useful for discovering popular items, monitoring new arrivals, or finding deals. While it doesn't explicitly state when not to use or name alternatives, the context is sufficient given sibling tool names.

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