Skip to main content
Glama

Yahoo! Auctions seller

run_yahoo_auctions_sellers
Read-onlyIdempotent

Get a Yahoo! Auctions Japan seller profile by seller id or URL: display name, rating count, positive-feedback percentage, store/verification badges and profile message. 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"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds genuinely new behavioral context: the field set returned and the operational cost ("Flat 5 points per successful run"), which is not in any structured field. It omits failure/not-found behavior and rate limits, keeping it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste: the primary action and accepted input forms come first, the return fields and cost follow. Nothing redundant or padded.

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?

With no output schema, the description carries the burden of describing returns and does so by listing the profile fields. It stops short of stating what happens for an invalid/missing seller, which would complete the picture for a single-parameter lookup.

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 coverage is 100% and the single parameter's schema description already says "Seller ID or URL" with an example. The description repeats this ("by seller id or URL") without adding format syntax or edge-case handling, so baseline 3 applies.

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 ("Get") and resource (Yahoo! Auctions Japan seller profile) and enumerates the fields returned (display name, rating count, positive-feedback %, badges, message). An agent can tell it apart from run_yahoo_auctions_items or run_yahoo_auctions_products, but it never explicitly names the sibling seller tools (sellers_items, sellers_reviews) to sharpen 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 Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The description assumes the agent already knows it wants a seller profile and does not route to run_yahoo_auctions_sellers_items or run_yahoo_auctions_sellers_reviews when the intent is listings or reviews.

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