Skip to main content
Glama
Sign In
keepa-adapter

keepa-adapter

by BWB03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keepa_analyze_bsr_trend

Analyze Amazon Best Seller Rank trends for ASINs over a set period and flag deterioration patterns to identify declining products. Get early warning signs of rank drops.

Instructions

Analyze BSR trend for ASINs over a period. Flags deterioration patterns.

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

Input Schema

NameRequiredDescriptionDefault
asinsYesASINs to analyze
domainNoAmazon domain (default: com)
period_daysNoAnalysis period in days (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It states that the tool 'flags deterioration patterns' but does not explain what this means in practice—whether it returns a list, a boolean, or modifies state. It also does not clarify if the operation is read-only or if any prerequisites (e.g., tracking) are required.

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 two sentences, front-loaded with the core purpose and a succinct note about the deterioration flagging. Every word earns its place, with no fluff or redundancy.

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?

There is no output schema, so the description must explain return values. The phrase 'flags deterioration patterns' is vague and does not specify what the tool actually returns or how the flags are presented. Given the moderate complexity of trend analysis, this is insufficient for an agent to fully anticipate the tool's behavior.

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?

All three parameters (asins, domain, period_days) have descriptions in the schema, giving 100% coverage. The description adds minimal extra meaning by mentioning 'ASINs' and 'period', which loosely map to asins and period_days, but provides no additional detail beyond the schema.

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 analyzes BSR trends for ASINs over a period and specifically flags deterioration patterns. This distinguishes it from siblings like get_price_history (price trends) and get_best_sellers (best seller lists), making the purpose specific and unambiguous.

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 for BSR trend analysis but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The clear subject matter gives context, but there is no comparative or conditional information.

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