Skip to main content
Glama

run_yahoo_auctions_sellers_reviews

Retrieve Yahoo! Auctions Japan seller feedback, including verdict, author, auction, comment, and date. Filter results by buyer/seller role and positive, neutral, or negative rating.

Instructions

Feedback comments left for a Yahoo! Auctions Japan seller: verdict, author, auction, comment text and relative date; filter by role and verdict. 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_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoRole. Options: as_seller = Received while selling, as_buyer = Received while buying
ratingNoVerdict. Options: positive = Positive, neutral = Neutral, negative = Negative
sellerYesSeller ID or seller page URL. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU (the token in /seller/{id})
max_itemsNoMax items (up to 500)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape (verdict, author, auction, comment text, relative date) plus a cost model ('1 point per returned record'). That cost disclosure is genuinely useful context beyond structured fields. It still omits pagination/auth behavior and rate limits, so not a 5.

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?

A single front-loaded sentence packs the resource, the returned fields, the filtering capability, and the cost model with no filler. It is slightly list-heavy but every clause earns its place.

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 read-only extraction tool with no annotations and no output schema, the description names the returned fields and the per-record cost, which is enough for an agent to call it correctly. Pagination behavior is left implicit, but the schema exposes start_page and max_items.

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%, including enum explanations for role and rating, so the baseline is 3. The description's 'filter by role and verdict' merely echoes parameters the schema already documents fully, adding no syntax or format detail beyond it.

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?

The description states a specific verb and resource — 'Feedback comments left for a Yahoo! Auctions Japan seller' — and enumerates the returned fields (verdict, author, auction, comment text, relative date). It does not explicitly differentiate itself from the sibling run_yahoo_auctions_sellers_reviews_summary, so the boundary between 'reviews' and 'reviews_summary' is left to inference.

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 phrase 'filter by role and verdict' implies how to narrow results but is really a parameter restatement rather than when-to-use guidance. There is no explicit statement of when to call this versus run_yahoo_auctions_sellers_reviews_summary or the seller/item siblings, and no exclusions.

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