Skip to main content
Glama
neuralverge

NeuralVerge

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_yahoo_auctions_items_search

Search live Yahoo! Auctions Japan listings by keyword or category, then filter by price, condition, region, seller, listing type, shipping, and sort to find relevant items.

Instructions

Search live Yahoo! Auctions Japan listings by keyword and/or category with price, buy-it-now, condition, region, seller, listing-type, appraisal, shipping filters and sort. 1 point per returned record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort 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
regionNoShipped 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
keywordNoSearch term (optional when a category is set). e.g. rolex
brand_idNoBrand ID
categoryNoCategory ID
conditionNoCondition. 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_imageNoWith photo only
max_itemsNoMax items (up to 500)
price_maxNoMax current price (JPY)
price_minNoMin current price (JPY)
start_pageNoStarting page
marketplaceNoMarketplace. Options: yahoo_auctions = Yahoo! Auctions, yahoo_flea = Yahoo! Flea Market
new_arrivalNoNewly listed only
seller_typeNoSeller type. Options: store = Store, individual = Individual
listing_typeNoListing type. Options: auction = Bidding auctions, fixed_price = Fixed price
authenticatedNoAuthenticity appraisal only
free_shippingNoFree shipping only
konbini_pickupNoConvenience-store pickup
keyword_excludeNoExcluded words (space-separated, needs a search term). e.g. box case
buy_now_price_maxNoMax buy-it-now price (JPY)
buy_now_price_minNoMin buy-it-now price (JPY)
anonymous_shippingNoAnonymous shipping
ending_within_hourNoEnding within 1 hour

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/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 usefully discloses the credit cost ('1 point per returned record') and that listings are 'live', but says nothing about pagination, authentication, or what happens to results beyond the page.

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?

Two tight sentences that front-load the core action and scope; the cost note is a second sentence that earns its place. No filler or repetition.

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 23-parameter tool with no annotations and no output schema, the description covers the searchable dimensions and cost but omits return format, pagination behavior, and result limits (e.g. max_items cap). Adequate but leaving real gaps for a complex tool.

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 one of the 23 parameters is already documented, including enums and ranges. The description's filter list (price, condition, region, seller, etc.) only mirrors the schema and adds no syntax or defaulting detail, so baseline 3 is correct.

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 (Search) and resource (live Yahoo! Auctions Japan listings) with a clear filter scope. The word 'live' implicitly separates it from the closed-search sibling, but no sibling is named explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives like run_yahoo_auctions_items_closed_search or run_yahoo_auctions_items. The 'keyword and/or category' phrasing hints at a minimum input but offers no exclusions or routing guidance.

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

Deploy Server

Other Tools