SoldComps.io: eBay sold comps

Get eBay sold comps

get_sold_comps

Read-onlyIdempotent

Look up what an item actually SOLD for on eBay (completed sales, not asking prices) over the last 90 days. Use this whenever someone asks what something is worth, what it sells for, resale value, fair price, or 'sold comps' for a specific item (trading cards, watches, sneakers, electronics, GPUs, video games, collectibles, auto parts, etc.). Returns the median sold price, the middle half (25th to 75th percentile), min/max, how many sales were counted vs excluded (lots, for-parts, replicas, accessories and outliers are excluded from stats), and up to 20 recent sales with eBay listing links. Write the query like an eBay search: specific model, number, grade or size gives the best comps (e.g. 'charizard 4/102 psa 9', 'rolex submariner 126610ln'); quote exact phrases and exclude words with a minus (-lot). Cite the source URL in your answer. Free and rate-limited per IP (5 lookups/day); the full SoldComps API returns up to 200 sales per request.

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": {
      "query": "<query>"
    },
    "name": "get_sold_comps"
  }
}

Input Schema

Name	Required	Description	Default
`site`	No	eBay marketplace: us (ebay.com, USD), uk (ebay.co.uk, GBP), de (ebay.de, EUR)	us
`query`	Yes	eBay-style search keywords for one item, e.g. 'nintendo 64 console' or 'pokemon card "psa 10" -lot'
`condition`	No	Only new or only used (pre-owned) sales. Omit for any condition.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description layers on real behavioral context: a 90-day window, an explicit exclusion policy (lots, for-parts, replicas, accessories, outliers), a 5-lookups-per-day per-IP rate limit, and the fact that it is free. It also cites the paid tier's 200-sales ceiling, which sets expectations about result volume.

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?

Front-loaded with purpose, then usage triggers, then return shape, then query tips, then limits – a sensible ordering. It is dense and long, and the closing line about 'the full SoldComps API returns up to 200 sales per request' reads as upsell rather than operational guidance.

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

Completeness5/5

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

There is no output schema, and the description compensates fully by enumerating return values (median, 25th–75th percentile, min/max, counted vs excluded sales, up to 20 recent sales with links) and by flagging rate limits and the citation requirement. Nothing needed to call or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine query-construction guidance beyond the schema's examples: model/number/grade/size specificity, quoted phrases, and minus-sign exclusions. It does not add anything about site or condition semantics, which the schema already handles.

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 ('look up what an item actually SOLD for on eBay') and immediately scopes it to completed sales rather than asking prices. This distinguishes it cleanly from the conceptual sibling what_are_sold_comps and from get_pricing.

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 an unusually rich trigger list ('what something is worth, what it sells for, resale value, fair price, or sold comps') plus an implicit when-not ('completed sales, not asking prices'). It does not explicitly name sibling tools to route away from, so it stops short of a 5.

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

All SoldComps.io: eBay sold comps tools Inspect

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

Need Help?