NeuralVerge Business Intelligence

Yahoo! Auctions seller items

run_yahoo_auctions_sellers_items

A seller's live Yahoo! Auctions Japan listings by seller id or URL, with keyword, category, price, condition, region and sort filters. 1 point per returned record.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort by. Options: newest = Newest, ending_soonest = Ending soonest, ending_latest = Ending latest, price_asc = Price: low to high, price_desc = Price: high to low, buy_now_price_asc = Buy-it-now: low to high, buy_now_price_desc = Buy-it-now: 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
`seller`	Yes	Seller ID or seller page URL. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU (the token in /seller/{id})
`keyword`	No	Search within the seller's listings. e.g. Keyword
`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 price (JPY)
`price_min`	No	Min price (JPY)
`start_page`	No	Starting page Default: 1.
`free_shipping`	No	Free shipping only
`keyword_exclude`	No	Excluded words (needs a keyword). e.g. box case

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

changedInput schema / properties / keyword_exclude / description

Previous value: -"Excluded words (needs a keyword). e.g. e.g. box case"New value: +"Excluded words (needs a keyword). e.g. box case"

changedInput schema / properties / seller / description

Previous value: -"Seller ID or seller page URL. e.g. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU (the token in /seller/{id})"New value: +"Seller ID or seller page URL. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU (the token in /seller/{id})"

AddedOct 1, 2026

TDQS

A3.5/5.0

Behavior3/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 does add two useful behavioral facts: the listings are 'live' (implying the closed-auction sibling is a different tool) and there is a cost model of '1 point per returned record'. It says nothing about rate limits, authentication, pagination behavior, or result structure.

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 sentences, zero filler. The core scope is front-loaded and the cost model is appended as a compact second sentence. Every clause earns its place.

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

Completeness3/5

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

For a 14-parameter, no-annotation, no-output-schema tool, the description covers purpose, filters and cost but leaves return-value shape, pagination semantics (start_page/max_items interaction) and auth expectations unexplained. Adequate but with real gaps given the tool's complexity.

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 including enums (sort, region, condition) is already documented in the schema. The description only enumerates filter families (keyword, category, price, condition, region, sort), which is a restatement of the schema rather than added meaning — baseline 3 applies.

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?

States a specific verb+resource+scope: a seller's live Yahoo! Auctions Japan listings, addressable by seller id or URL. The 'seller's listings' scope inherently separates it from global search siblings like run_yahoo_auctions_items_search and from the seller-profile tool run_yahoo_auctions_sellers, though it never names those alternatives.

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?

Usage is implied by the scope phrase 'A seller's live listings by seller id or URL' — an agent can infer this is the tool for enumerating one seller's inventory. There is no explicit when-to-use/when-not statement or routing to the closed-auction or global-search siblings.

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?