Skip to main content
Glama
Sign In
NeuralVerge

NeuralVerge

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_vinted_users_items

Fetch a Vinted member's current wardrobe listings by user ID or profile URL, including titles, prices, brands, sizes, conditions, photos, favourites, and item status flags.

Instructions

A Vinted member's current wardrobe: title-level data, prices, brand, size, condition, photos, favourites and reserved/closed/hidden flags. 1 point per returned record.

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": {
      "user": "<user>"
    },
    "name": "run_vinted_users_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUser ID or profile URL. e.g. 103792107 or https://www.vinted.de/member/103792107-katieronja
domainNoDomain. Options: vinted.de = vinted.de, vinted.fr = vinted.fr, vinted.es = vinted.es, vinted.it = vinted.it, vinted.nl = vinted.nl, vinted.pl = vinted.pl, vinted.co.uk = vinted.co.uk
max_itemsNoMax items (up to 500)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return-field set and the cost model ('1 point per returned record'), which is genuine behavioral value. But it omits read-only status, pagination semantics for start_page/max_items, and any rate-limit or auth context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the resource description front-loaded and the cost note trailing. No wasted prose, though the field enumeration is dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a listing tool with no output schema and no annotations, the description partially compensates by naming the returned fields. It still leaves pagination behavior, read-only nature, and sibling differentiation unaddressed, leaving gaps an agent would need to resolve.

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 four parameters are already documented in the schema. The description adds no parameter-level detail beyond the field list of results, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource: a Vinted member's current wardrobe (their listed items), and enumerates the fields returned. It does not, however, distinguish this from siblings like run_vinted_users, run_vinted_users_feedbacks, or run_vinted_products_search, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no mention of the alternative tools. The agent can only infer usage from the description of the returned data; nothing routes it against the sibling Vinted tools.

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