Skip to main content
Glama
Sign In
keepa-adapter

keepa-adapter

by BWB03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keepa_get_seller_stats

Get per-seller buy box stats for ASINs: win percentage, average price, and FBA status.

Instructions

Get buy box statistics per seller for ASINs, including win percentage, average price, and FBA status.

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": {
      "asins": "<asins>"
    },
    "name": "keepa_get_seller_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinsYesASINs to get seller stats for
domainNoAmazon domain (default: com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention any potential side effects, authentication requirements, rate limits, data freshness, or limitations. While 'Get' suggests read-only, important behavioral context is missing.

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?

The description is a single, focused sentence that immediately states the core purpose and includes valuable details about the output. There is no redundant or filler content, making it highly efficient.

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?

The tool has 2 parameters, no output schema, and no annotations. The description lists key return elements but leaves ambiguity about time range, grouping, and how sellers are identified. It is adequate for a simple tool but lacks some contextual details that would make it fully self-contained.

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 each parameter already has a description. The tool description adds some semantic context by mentioning the output (win percentage, average price, FBA status) but does not provide additional parameter-level meaning beyond what the schema already offers.

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?

The description clearly states the tool fetches buy box statistics per seller for ASINs, specifically listing win percentage, average price, and FBA status. This is a specific verb+resource+scope that distinguishes it from siblings like keepa_get_buy_box or keepa_get_price_history.

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 implies the tool is for obtaining per-seller buy box stats but does not explicitly state when it should be used over alternatives or when not to use it. No sibling comparisons or exclusions are provided, leaving usage guidance implied rather than explicit.

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