Skip to main content
Glama

run_yahoo_auctions_sellers_reviews_summary

Retrieve a Yahoo! Auctions Japan seller's feedback summary, including total score, positive percentage, and positive/neutral/negative counts for multiple periods.

Instructions

Aggregated Yahoo! Auctions Japan feedback score of a seller: total and positive percentage as seller/buyer plus positive/neutral/negative counts over the last week, month, 6 months, 100 and 1000 transactions. Flat 5 points per successful run.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesSeller ID or URL. e.g. 8bdaxRiVapnRAmjjt2iWjM9wQzLXU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/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 provides strong behavioral context by detailing the exact output (total and positive percentage, counts over specific periods) and credit cost. It does not explicitly state read-only status or error behavior, but for a retrieval tool this is a minor gap.

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?

The description is front-loaded with the core purpose and then adds a concise note about credit cost. Two sentences with no wasted words, though the long first sentence could be slightly more structured.

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 simple one-parameter tool with no output schema, the description adequately explains return values and pricing. It is nearly complete, lacking only explicit usage guidance and operational details like read-only status.

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 the schema already fully documents the single 'seller' parameter. The description adds no additional meaning or constraints beyond what the schema provides, making the baseline 3 appropriate.

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 (Yahoo! Auctions Japan seller feedback) and the aggregated metrics returned, differentiating itself from detailed review tools by emphasizing 'aggregated' and 'summary'. It does not explicitly name sibling alternatives, so it falls short of a perfect 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?

No explicit guidance on when to use this tool versus alternatives such as run_yahoo_auctions_sellers_reviews or run_yahoo_auctions_sellers. Usage is only implied by the purpose statement.

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