Skip to main content
Glama

ads_list_sb_targets

Read-only

LIVE: product target Sponsored Brands (ASIN/categoria/brand) con BID e stato ATTUALI. Il target_id serve per ads_update_sb_target_bid. NON ritorna performance: usa execute_sql sul data-hub. Elenco vuoto = nessun target SB su questo profilo: dillo, NON inventare target.

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

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.
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
ad_group_idNoId ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups).
campaign_idNoId campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns).
state_filterNoFiltra per stato: array con ENABLED, PAUSED, ARCHIVED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Id ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups)."
    • addedInput schema / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
    • addedInput schema / properties / state_filter / description
      Added value: +"Filtra per stato: array con ENABLED, PAUSED, ARCHIVED."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds that data is live/current rather than historical, that performance metrics are NOT included, and how to interpret an empty list. It stops short of describing pagination, result caps, or ordering, which keeps it from a 5.

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?

Four short sentences, each carrying distinct information: freshness, the cross-tool link, the exclusion of performance data, and empty-result handling. The most actionable constraint (LIVE data) is front-loaded with no 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 read-only list tool with no output schema, the description covers what comes back (target type, bid, state), what does not (performance), and the empty case. Only result volume/pagination behavior is left unspecified, a minor gap given the annotations carry the safety profile.

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 all five parameters (account_id, profile_id, ad_group_id, campaign_id, state_filter) are already documented in the schema. The description adds no filter syntax or scoping detail beyond that; target_id is a returned field, not an input parameter.

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?

States a specific resource (Sponsored Brands product targets, with ASIN/category/brand types) and explicitly says it returns CURRENT bid and state, which distinguishes it from keyword/ad-group siblings. It also names the consuming tool (ads_update_sb_target_bid) and explicitly excludes performance data, routing that need to execute_sql.

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?

Gives explicit when-to-use (retrieve target_id for bid updates), when-not-to-use (performance data -> execute_sql on the data-hub), and a behavioral instruction for the empty-result case (say so, do not invent targets). The alternative is named with the condition that selects it.

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