Skip to main content
Glama

Yahoo! Auctions seller items

run_yahoo_auctions_sellers_items
Read-onlyIdempotent

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.

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": {
      "seller": "<seller>"
    },
    "name": "run_yahoo_auctions_sellers_items"
  }
}

Input 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
sellerYesSeller ID or seller page URL. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU (the token in /seller/{id})
keywordNoSearch within the seller's listings. e.g. Keyword
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 price (JPY)
price_minNoMin price (JPY)
start_pageNoStarting page Default: 1.
free_shippingNoFree shipping only
keyword_excludeNoExcluded words (needs a keyword). e.g. box case

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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})"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description goes beyond them by disclosing 'live' listings (contrasting with the closed-auction sibling) and the bimonthly cost model '1 point per returned record' — a material trait no annotation or schema field carries.

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 compact sentences: the scope and input key come first, filters second, and the point-cost disclosure last. No filler, no restatement of the tool name.

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 1-required-param listing tool with full annotation coverage and full schema coverage, the description gives the essentials plus cost. With no output schema it could say slightly more about the shape of a returned record, but 'listings' plus the per-record charge is sufficient to call it correctly.

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's meaning, enums, ranges and defaults are already documented. The description's enumeration of 'keyword, category, price, condition, region and sort filters' summarizes those same fields without adding syntax or format detail, matching the baseline 3 for a fully-described schema.

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 resource and scope: a seller's live Yahoo! Auctions Japan listings, keyed by seller id or URL. The word 'live' and the seller-scoping implicitly separate it from run_yahoo_auctions_items_search and run_yahoo_auctions_items_closed_search, but no sibling is named explicitly, so an agent must infer the boundary.

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 rather than stated: 'by seller id or URL' tells the agent what it must already have to call the tool, but there is no explicit when-to-use vs. when-to-prefer-an-alternative guidance, nor any note that seller IDs can be obtained from run_yahoo_auctions_sellers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources