Skip to main content
Glama
Sign In
keepa-adapter

keepa-adapter

by BWB03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keepa_list_promos

List promotional events for a specific ASIN or all tracked ASINs, with optional filtering by Amazon domain and active status.

Instructions

List promotional events for an ASIN or all tracked ASINs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keepa_list_promos"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinNoFilter by ASIN
domainNoAmazon domain (default: com)
active_onlyNoOnly show active promos (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the action. It does not confirm read-only behavior, auth needs, data scope, or return format. The minimal wording gives no additional behavioral context.

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, well-structured sentence that front-loads the verb and resource. Every word contributes value, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description is too thin. It does not mention what constitutes a promotional event, potential result size, pagination, or any limitations. For a listing tool with three optional parameters, more context is needed to fully guide an agent.

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%, so the baseline is 3. The description adds a slight nuance by clarifying that omitting 'asin' means 'all tracked ASINs', which goes beyond the schema's 'Filter by ASIN'. However, it does not elaborate on domain or active_only, so it stays at the baseline.

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 uses a specific verb 'List' and names the resource 'promotional events' with scope ('for an ASIN or all tracked ASINs'). It clearly distinguishes from mutating siblings like keepa_add_promo and keepa_analyze_promo_impact, though it doesn't explicitly differentiate from keepa_get_deals.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or preferred scenarios, leaving the agent without contextual decision support.

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