Skip to main content
Glama

Soldgraph

by io.github.soldgraph
OverviewDiscussionsAdmin

Vinted active listings

vinted_listings
Read-onlyIdempotent

Search one page of Vinted active listings by keyword, on Vinted US, UK or 24 European sites, 96 rows a page. Prices are seller asks. No sold search. Results are cached for 15 minutes. Each completed search costs 1 request, cache hits included; failed searches are free. Docs: https://soldgraph.com/docs/api/vinted-listings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keywords, 1–200 characters, as you'd type them into the marketplace's search box. Be specific: model, size, grade, edition.
pageNoPage to fetch, 1 to 10. Vinted serves 96 rows a page and stops at 960 results. Follow next_page until it is null. Optional.
sortNoVinted's own ranking, newest listed first, or item price low to high or high to low. best_match mixes in promoted listings, flagged with promoted.best_match
fieldsNosummary keeps the fields most agents need; full returns every field the API returns.summary
countryNoWhich Vinted site to search: us (vinted.com), uk (vinted.co.uk) or a European site such as fr, de, it, es, nl or pl. Results, prices, min_price and max_price use that site's currency. Optional.us
brand_idNoVinted numeric brand ID, such as 53 for Nike or 10 for Levi's. Keeps only that brand. Find one as brand_id on /v1/vinted/item. Optional.
conditionNoVinted's own conditions. Send one or more, separated by commas, like new_with_tags,very_good. Vinted applies the filter.
max_priceNoHighest price, in whole units of the country's currency (US dollars for us). Optional. You can send it without min_price.
min_priceNoLowest price, in whole units of the country's currency (US dollars for us). Optional. Must not be more than max_price. You can send it without max_price.
category_idNoVinted numeric category ID, such as 1242 for men's trainers. Keeps only listings in that category. Find one as category.id on /v1/vinted/item. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses non-obvious operational traits: 15-minute result caching, a 1-request cost even on cache hits, failed searches being free, and that prices are seller asks rather than transaction prices. This is exactly the context annotations cannot convey.

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?

Four short sentences, front-loaded with what the tool is and what it is not, followed by cost/caching facts. No filler and nothing buried.

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?

For a 10-parameter search tool with no output schema and full schema coverage, the description covers scope, geographies, pagination size, caching and cost. It stops short of describing result shape or how 'next_page' terminates, though the schema's page description partly covers that.

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 every parameter is already documented (including currency behaviour, brand/category ID lookups, and next_page). The description adds almost nothing parameter-specific beyond repeating that searches span US/UK/EU sites. 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 ('Search one page of Vinted active listings by keyword') and scopes it to a geography. The 'No sold search' clause disambiguates it from sold-data siblings such as ebay_sold, poshmark_sold and mercari_sold without needing the schemas.

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 a clear exclusion ('No sold search'), pagination workflow ('96 rows a page', implied by the schema's next_page), and a docs URL. It never names a concrete alternative sibling for sold data, so routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Soldgraph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources