Skip to main content
Glama

ads_list_sp_targets

Read-only

List SP targeting clauses — SIA i target MANUAL (ASIN/categoria) SIA i 4 gruppi AUTO che Amazon genera da solo nelle campagne AUTO. Ogni clause ritorna il suo targetId, lo state e (se impostato) il bid. Mappatura gruppi AUTO (expression.type → nome UI): QUERY_HIGH_REL_MATCHES=close-match, QUERY_BROAD_REL_MATCHES=loose-match, ASIN_SUBSTITUTE_RELATED=substitutes, ASIN_ACCESSORY_RELATED=complements. PER CAMBIARE IL BID DI UN GRUPPO AUTO: chiama questo tool con campaign_id → prendi il targetId del gruppo → ads_update_sp_target_bid(target_id, bid). NON usare ads_create_* sulle AUTO (i target esistono già). Paginazione: all_pages=true di default, next_token per riprendere, complete/truncated per verificare la completezza.

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

Input Schema

NameRequiredDescriptionDefault
all_pagesNotrue = legge tutte le pagine; false = una sola pagina.
page_sizeNoRighe per pagina (intero).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
next_tokenNoToken di paginazione restituito dalla chiamata precedente.
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. Changed3 schema fields changed
    • addedInput schema / properties / all_pages
      Added value: +{
      +  "default": true,
      +  "description": "true = legge tutte le pagine; false = una sola pagina.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / next_token
      Added value: +{
      +  "description": "Token di paginazione restituito dalla chiamata precedente.",
      +  "type": "string"
      +}
    • addedInput schema / properties / page_size
      Added value: +{
      +  "default": 200,
      +  "description": "Righe per pagina (intero).",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. 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."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description still contributes a lot beyond that: the return fields per clause, the expression.type → UI-name mapping for the four AUTO groups (QUERY_HIGH_REL_MATCHES=close-match, etc.), and the complete/truncated completeness signal. It stops short of stating permission/auth requirements or rate limits, which keeps it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but well ordered: purpose, then AUTO mapping, then the bid workflow, then pagination. Some content (all_pages default, next_token) restates the schema, and the Italian/English mixing makes it slower to parse, but every sentence contributes actionable information.

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?

With no output schema, the description correctly supplies the return contract (targetId, state, optional bid, complete/truncated). It is lighter on the MANUAL-campaign side and never mentions ad_group_id or state_filter, though the schema documents those fully, so there is no blocking gap.

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 the baseline is 3; the description earns an extra point by giving campaign_id a purpose the schema does not (it is the entry point for locating AUTO-group targetIds before bidding) and by documenting next_token and all_pages as a pagination loop with a completeness check.

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?

Opens with a specific verb+resource ('List SP targeting clauses') and immediately splits the resource into the two meaningful categories: MANUAL (ASIN/category) and the 4 AUTO groups Amazon generates itself. It also states what each clause returns (targetId, state, bid), so an agent knows the shape of the result without opening the 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?

Gives an explicit workflow for the non-obvious case (to change an AUTO group bid: call this tool with campaign_id, take the targetId, then call ads_update_sp_target_bid) and an explicit prohibition ('NON usare ads_create_* sulle AUTO — i target esistono già'). The alternative tool is named, and the condition that selects it is stated.

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