Skip to main content
Glama

get_competitive_pricing

Read-only

READ-ONLY. Buy Box / Featured Offer price per ASIN (max 20 per Amazon call, auto-batched). Returns buy_box_price (listing) + buy_box_landed_price (incl. shipping), condition, whether you win the Buy Box, and source. Falls back to live offers when Amazon has no competitive price, so it returns far fewer nulls than the raw SP-API. Use for a few ASINs; for a long list use get_buybox_prices.

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": "get_competitive_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinsYesElenco di ASIN Amazon (array di stringhe, es. ["B08N5WRWNW"]).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / asins / description
      Added value: +"Elenco di ASIN Amazon (array di stringhe, es. [\"B08N5WRWNW\"])."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds genuinely new behavior: automatic batching at 20 ASINs per Amazon call and a fallback to live offers when no competitive price exists, which explains why nulls are rarer. It stops short of stating rate limits or partial-failure behavior, so it is strong but not exhaustive.

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?

Front-loaded with the mode and the core resource, then return fields, then fallback caveat, then the disambiguation sentence. Every sentence carries distinct information; 'READ-ONLY' mildly repeats the annotation but is a defensible opener.

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

Completeness5/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 carries the return-shape burden and does so by naming the key fields and the win/loss indicator. Combined with batching and fallback disclosure, an agent has everything needed to call this correctly for a short ASIN list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), and the description adds useful semantics for the asins array: the 20-per-call cap and auto-batching mean the agent need not chunk the list itself. It adds nothing about account_id, which the schema already documents.

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?

Precise verb+resource: returns Buy Box / Featured Offer price per ASIN, and enumerates the returned fields (buy_box_price, buy_box_landed_price, condition, win/loss, source). It also names the sibling it is not for, so an agent can distinguish it from get_buybox_prices without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit routing rule: 'Use for a few ASINs; for a long list use get_buybox_prices.' That is a concrete when-to-use plus a named alternative, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources