Skip to main content
Glama

NeuralVerge Business Intelligence

by ai.neuralverge.api
OverviewDiscussionsAdmin

Yahoo! Auctions items search

run_yahoo_auctions_items_search

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) Default: 25.
price_maxNoMax current price (JPY)
price_minNoMin current price (JPY)
start_pageNoStarting page Default: 1.
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. Changed1 schema field changed
    • changedInput schema / properties / keyword_exclude / description
      Previous value: -"Excluded words (space-separated, needs a search term). e.g. e.g. box case"New value: +"Excluded words (space-separated, needs a search term). e.g. box case"
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It usefully discloses the billing model ("1 point per returned record"), which the schema does not, but says nothing about authentication needs, pagination behavior, or what a result contains.

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-loaded with purpose and filters, followed by the cost note. No filler or redundancy.

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 purpose and filter scope but omits pagination behavior (max_items, start_page), whether keyword and category combine, and the shape of returned records. Adequate but with clear gaps.

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 all 23 parameters are already documented, establishing a baseline of 3. The description adds an aggregate summary of the filter families (price, buy-it-now, condition, region, seller, listing-type, appraisal, shipping, sort) but no syntax or interaction details beyond the schema.

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 ("Search live Yahoo! Auctions Japan listings") and the word "live" implicitly distinguishes it from the sibling run_yahoo_auctions_items_closed_search, which covers closed listings. An agent can identify the tool's domain without opening the schema.

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 establishes the search context ("by keyword and/or category"), implying when to use it, and "live" hints at the contrast with closed-search siblings. However, it never explicitly names an alternative or states when not to use this tool, leaving routing to inference.

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 toolsInspect
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