NeuralVerge Business Intelligence

Yahoo! Auctions closed items search

run_yahoo_auctions_items_closed_search

Search completed Yahoo! Auctions Japan auctions by keyword and see the price each item actually sold for, with sold-price, condition, region, seller-type and sort filters. 1 point per returned record.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort by. Options: ended_recent = Recently ended, ended_oldest = Oldest ended, price_asc = Sold price: low to high, price_desc = Sold price: high to low, bids_desc = Most bids, bids_asc = Fewest bids, popular = Popular, featured = Featured
`region`	No	Shipped from. Options: hokkaido = Hokkaido, aomori = Aomori, iwate = Iwate, miyagi = Miyagi, akita = Akita, yamagata = Yamagata, fukushima = Fukushima, ibaraki = Ibaraki, tochigi = Tochigi, gunma = Gunma, saitama = Saitama, chiba = Chiba, tokyo = Tokyo, kanagawa = Kanagawa, yamanashi = Yamanashi, nagano = Nagano, niigata = Niigata, toyama = Toyama, ishikawa = Ishikawa, fukui = Fukui, gifu = Gifu, shizuoka = Shizuoka, aichi = Aichi, mie = Mie, shiga = Shiga, kyoto = Kyoto, osaka = Osaka, hyogo = Hyogo, nara = Nara, wakayama = Wakayama, tottori = Tottori, shimane = Shimane, okayama = Okayama, hiroshima = Hiroshima, yamaguchi = Yamaguchi, tokushima = Tokushima, kagawa = Kagawa, ehime = Ehime, kochi = Kochi, fukuoka = Fukuoka, saga = Saga, nagasaki = Nagasaki, kumamoto = Kumamoto, oita = Oita, miyazaki = Miyazaki, kagoshima = Kagoshima, okinawa = Okinawa, overseas = Overseas
`keyword`	Yes	Search term. e.g. rolex
`brand_id`	No	Brand ID
`category`	No	Category ID
`condition`	No	Condition. Options: new = New, used = Used (any), like_new = Like new, no_visible_damage = No visible damage, slight_damage = Slight damage, damaged = Damaged, poor = Poor condition
`has_image`	No	With photo only
`max_items`	No	Max items (up to 500) Default: 25.
`price_max`	No	Max sold price (JPY)
`price_min`	No	Min sold price (JPY)
`start_page`	No	Starting page Default: 1.
`seller_type`	No	Seller type. Options: store = Store, individual = Individual
`free_shipping`	No	Free shipping only
`keyword_exclude`	No	Excluded words (space-separated). e.g. box case

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / keyword_exclude / description

Previous value: -"Excluded words (space-separated). e.g. e.g. box case"New value: +"Excluded words (space-separated). e.g. box case"

AddedOct 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses the metered cost ('1 point per returned record'), which is genuinely useful billing behavior an agent can't get elsewhere. It is clearly a read-only search operation, but it omits result-volume/pagination behavior beyond the schema defaults.

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?

Two tight sentences front-load the resource and the key value proposition (real sold prices), with the cost disclosure appended. No filler or repetition of the title.

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 14-parameter search with no output schema, the description conveys the query domain, the filter surface, and the per-record cost. It slightly under-delivers on what a returned record contains and pagination limits, but the schema covers those inputs adequately.

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 the schema already documents all 14 parameters and their enum option meanings. The description echoes the filter categories (sold-price, condition, region, seller-type, sort) but adds no syntax or format guidance beyond the schema, so the 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 (Search) and a precisely scoped resource: completed Yahoo! Auctions Japan listings, plus the distinctive outcome (actual sold price). The word 'completed/closed' cleanly separates it from the active-listing sibling run_yahoo_auctions_items_search without needing to open either schema.

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?

The 'completed auctions / price each item actually sold for' framing tells the agent this is the tool for historical sold-price research rather than live listings, and it lists the available filter dimensions. It stops short of naming the active-search sibling explicitly, so the routing is implied 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 NeuralVerge Business Intelligence 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?