Skip to main content
Glama

Find comparable listings

search_similar_items
Read-only

Find comparable Vinted listings for your item. Provide visible details like brand, model, size, and colour to get filtered results with rejection reasons, helping justify your price.

Instructions

Finds listings genuinely comparable to an item you are about to sell. Give it the facts you can actually see in the photos (brand, model, capacity, size, colour). It tries several search phrasings, then removes duplicates, accessories, broken/for-parts listings, different capacities and mismatched sizes. Returns both the kept comparables and why each rejected result was dropped, so you can justify the price to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoSize as printed on the label, e.g. "M", "42", "US 9.5".
brandNoBrand exactly as it appears on the item. Do not guess.
colorNoMain colour, in the storefront language where possible.
modelNoModel or product name, e.g. "Air Max 90", "iPhone 13".
notesNoAnything else worth telling a buyer, e.g. "original box included".
genderNo
countryNoVinted storefront to use (fr, be, de, at, es, it, nl, pt, …). Defaults to the server's configured country.
defectsNoEvery visible flaw: stains, scuffs, missing buttons. These are always kept in the description.
queriesNoExtra search phrasings to try on top of the ones derived from the facts.
capacityNoStorage or volume, e.g. "128 GB", "50 ml".
categoryNoFree-text category guess, e.g. "sneakers", "winter coat".
materialNoMaterial, e.g. "cotton", "leather".
conditionNoVinted's five condition levels. Pick the one the photos actually support.
referenceNoReference / SKU / colourway code if visible on a label or the item.
maxResultsNo
requireSizeNoKeep only results whose size matches. Useful for clothing.
minSimilarityNoSimilarity floor, 0..1. Default 0.25. Raise it for a stricter comparable set.
secondaryColorNoSecond colour, if the item is clearly two-tone.
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses non-obvious behavior: it 'tries several search phrasings,' removes duplicates/accessories/broken/mismatched items, and returns both kept comparables and rejection reasons. This is rich, non-obvious behavioral context with no contradiction.

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 sentences: purpose, input guidance, and behavioral detail. It is front-loaded with the core purpose, every sentence adds information, and there is no fluff.

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 tool with 18 parameters and no output schema, the description explains the output format (kept items plus rejection reasons) and the core filtering logic, which is essential context. It does not address default behavior or explicitly compare with get_similar_items, but the schema and annotations cover most parameter semantics and safety profile.

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 high (89%), so the baseline is 3. The description adds mild semantic value by identifying 'brand, model, capacity, size, colour' as photo-visible facts, but does not elaborate on parameters beyond what the schema already provides.

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 states it 'Finds listings genuinely comparable to an item you are about to sell' and details the filtering and output, making the purpose specific. However, the sibling 'get_similar_items' exists and the description does not explicitly differentiate itself from that similarly named tool.

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

Usage Guidelines3/5

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

It provides context: use when about to sell an item and give facts visible in photos, and mentions returning rejection reasons 'so you can justify the price to the user.' No explicit exclusions or comparisons with alternatives like search_items or get_similar_items are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rachid598/mcpvin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server