Skip to main content
Glama
Sign In
keepa-adapter

keepa-adapter

by BWB03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keepa_get_best_sellers

Retrieve the list of best-selling ASINs for any Amazon category. Provide the category ID and domain to get top products for market research and competitive analysis.

Instructions

Get the best seller ASIN list for a category.

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": {
      "category": "<category>"
    },
    "name": "keepa_get_best_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoAmazon domain (default: com)
categoryYesCategory ID to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not disclose response format, sorting order, rate limits, errors, or whether the list is live or historical. This is minimal behavioral information.

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, concise sentence with no fluff. It is front-loaded with the action and resource, making it easy to parse. There are no unnecessary words.

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 schema covers parameters fully, but with no output schema, the description should clarify return semantics. It states 'ASIN list' which implies the core output, but does not specify structure, limits, or potential edge cases. It is adequate for a simple tool but has clear gaps.

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?

The input schema already describes both parameters: 'domain' with a default and 'category' as an ID. Since schema coverage is 100%, the description adds no value beyond the schema, warranting the baseline score of 3.

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 uses a specific verb 'Get' with a clear resource 'best seller ASIN list' and scope 'for a category'. It clearly distinguishes from sibling tools like keepa_get_product and 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites such as how to obtain a valid category ID. Users are left without contextual direction.

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