Skip to main content
Glama

ads_catalog_coverage

Read-only

READ-ONLY. Tutti gli ASIN del catalogo e delle vendite recenti di un outpost, uno per uno, con SKU, titolo, stock, vendite e copertura Sponsored Products LIVE. Incrocia tutte le Product Ads e gli stati campagna/gruppo. Nessun campionamento; dati incompleti o obsoleti producono errore, mai falsi scoperti. Per prodotti venduti senza SP attive usare only_with_sales=true e only_uncovered=true. Richiede data-hub sincronizzato e Ads collegate.

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

Input Schema

NameRequiredDescriptionDefault
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
lookback_daysNoGiorni di storico da considerare (intero, es. 30).
only_in_stockNotrue = solo prodotti con stock disponibile.
only_uncoveredNoSolo sp_covered=false, inclusi gli esauriti se only_in_stock=false
only_with_salesNotrue = solo prodotti con vendite nel periodo.
ignore_orphan_adsNoSe Amazon non restituisce alcune campagne/gruppi referenziati dalle Product Ads, esclude quegli annunci orfani (non in erogazione) invece di fermarsi; il risultato li elenca in orphan_ad_ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / lookback_days / description
      Added value: +"Giorni di storico da considerare (intero, es. 30)."
    • addedInput schema / properties / only_in_stock / description
      Added value: +"true = solo prodotti con stock disponibile."
    • addedInput schema / properties / only_with_sales / description
      Added value: +"true = solo prodotti con vendite nel periodo."
  2. Changed1 schema field changed
    • addedInput schema / properties / ignore_orphan_ads
      Added value: +{
      +  "default": false,
      +  "description": "Se Amazon non restituisce alcune campagne/gruppi referenziati dalle Product Ads, esclude quegli annunci orfani (non in erogazione) invece di fermarsi; il risultato li elenca in orphan_ad_ids.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: no sampling, incomplete or stale data causes an error rather than false uncovered results, and all Product Ads plus campaign/ad-group states are cross-referenced. It also adds operational prerequisites that an agent must know before invoking the tool.

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 definition is front-loaded with READ-ONLY and the core scope, then moves through behavior, the key filter combination, and prerequisites. It is dense but every sentence carries specific operational information, with no redundant filler.

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

Completeness4/5

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

For a complex, read-only coverage report with no output schema, the description covers scope, listed output fields, error semantics, and prerequisites well. It stops short of fully specifying result ordering, pagination, or how orphan_ad_ids appear in the output, so it is strong but not completely exhaustive.

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%, so parameter definitions already do most of the work. The description still adds meaningful semantic guidance by explaining the combination only_with_sales=true and only_uncovered=true for finding sold products without active SP, which is not captured by the individual schema field descriptions.

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 states a specific resource and scope: every ASIN in an outpost's catalog and recent sales, with SKU, title, stock, sales, LIVE Sponsored Products coverage, and cross-referenced Product Ads/campaign states. It is clearly distinguishable in purpose, though it does not explicitly contrast itself with sibling audit or catalog-search tools.

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

Usage Guidelines4/5

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

It gives a concrete usage condition: for sold products without active SP, use only_with_sales=true and only_uncovered=true. It also states prerequisites, a synced data-hub and linked Ads, but does not provide explicit when-not-to-use guidance or named alternatives.

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