L50 UK Data API

reverb search

reverb_search

Read-only

Live Reverb (music gear marketplace) listings for a keyword: a market summary (median asking price by condition, share taking offers, top makes, cheapest with postage) plus up to 100 listings with price, postage, condition, make, model and year. Costs $0.05 per call, paid in USDC on Base with x402.

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": {
      "keyword": "<keyword>"
    },
    "name": "reverb_search"
  }
}

Input Schema

Name	Required	Description
`max`	No	Listings to return (default 50)
`keyword`	Yes	What to search for, e.g. fender stratocaster or boss ds-1
`shipsTo`	No	Country code, e.g. GB: only listings shipping there, with postage
`currency`	No	Price currency (default GBP)
`priceMax`	No	Max price
`priceMin`	No	Min price
`condition`	No	Condition (default any)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds important behavior beyond them: it returns a market summary plus up to 100 listings, and it costs $0.05 per call paid in USDC on Base via x402. It does not describe rate limits or failure behavior, but the paid-call disclosure is substantial context.

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?

The description is compact and front-loaded: the resource and output scope come first, followed by the cost and payment mechanism. Every sentence carries useful information, with no filler.

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 paid, open-world search tool with no output schema, the description gives a clear picture of the returned data and the cost model. It is nearly complete, though it could say more about pagination limits, latency, or what happens when no listings match.

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 coverage is 100%, so all seven parameters are already documented in the input schema. The description adds output-oriented context such as up to 100 listings and which listing fields are returned, but it does not add meaning beyond the schema for parameters like shipsTo, priceMin, priceMax, or condition.

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 states a specific verb and resource: live Reverb music-gear marketplace listings for a keyword. It identifies Reverb explicitly, which distinguishes it from sibling marketplace searches such as poshmark_search, vinted_search, and ebay_market.

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?

The description makes clear this is the Reverb-specific marketplace search, but it does not explicitly say when to use it instead of compare_resale or the other marketplace tools. Usage is implied by the marketplace name rather than stated as routing guidance.

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

All L50 UK Data API 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?