Skip to main content
Glama
Sign In
keepa-adapter

keepa-adapter

by BWB03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keepa_get_deals

Get coupon history, active promotions, and lightning deal data for Amazon ASINs to monitor discount trends.

Instructions

Get coupon history, active promotions, and lightning deal data for ASINs.

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

Input Schema

NameRequiredDescriptionDefault
asinsYesASINs to get deal data 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation ('Get') but does not mention side effects, authorization requirements, rate limits, or any other behavioral nuances beyond the basic action.

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, front-loaded sentence that directly states the tool's purpose with no filler or redundant details. Every word earns its place.

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?

For a simple get-by-ASIN tool, the description is adequate but leaves gaps. There is no output schema, so the description should hint at return structure, and the 'domain' parameter behavior is not explained. However, the tool itself is relatively straightforward, so it is minimally complete.

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 baseline is 3. The description adds no additional semantics beyond what the schema already states, such as that 'asins' are the target identifiers and 'domain' is optional with a default. It does not enrich parameter understanding.

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 the specific verb 'Get' and explicitly names the resources: coupon history, active promotions, and lightning deal data for ASINs. This clearly distinguishes it from sibling tools like get_product or get_price_history, which target different data.

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 usage when deal-related data is needed, but provides no explicit alternatives or exclusions. It does not mention when to prefer other tools or any prerequisites, so guidance is only implicit.

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