Skip to main content
Glama

ads_list_sp_audiences

Read-only

READ-ONLY. Elenca i SEGMENTI DI PUBBLICO utilizzabili per i moltiplicatori di bid delle campagne Sponsored Products (audience bid adjustments, disponibili in IT/DE/FR/ES/UK). source: "amazon" (default: pubblici costruiti da Amazon, es. chi ha già comprato dal brand, chi ha cliccato o messo nel carrello, alta probabilità di acquisto), "amc" (pubblici creati in Amazon Marketing Cloud) o "all". search = filtro testuale opzionale. Ritorna audience_id, name, description, source. Gli audience_id vanno passati a ads_update_sp_audience_bidding; i segmenti già impostati su una campagna si leggono in ads_list_sp_campaigns (audience_adjustments). NON inventare audience_id: se la lista è vuota dillo all'utente.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLingua dei nomi, es. it_IT, de_DE, en_GB (opzionale)
searchNoFiltro testuale sul nome del pubblico (opzionale)
sourceNoOrigine dei segmenti: amazon, amc o all.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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 / source / description
      Added value: +"Origine dei segmenti: amazon, amc o all."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description reinforces READ-ONLY and adds useful behavior beyond annotations: the returned fields audience_id, name, description, and source, plus the downstream handoff to ads_update_sp_audience_bidding. Pagination or rate-limit behavior is not covered, which keeps this below 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.

Conciseness4/5

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

The description is front-loaded with READ-ONLY and the core purpose, then moves into source semantics, return fields, and downstream usage. It is somewhat dense but every sentence carries operational value, especially the routing to ads_update_sp_audience_bidding and the warning against inventing IDs.

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?

There is no output schema, so the description usefully compensates by naming the returned fields and explaining how results connect to sibling tools. It also covers marketplace availability and empty-list handling. It could be more complete by mentioning whether results are paginated or capped, but it is otherwise sufficient for a read-only list tool.

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 description coverage is 100%, so the schema already documents all five parameters. The description still adds semantic value for source by explaining what amazon, amc, and all mean in practice, including examples of Amazon-built audiences. It does not elaborate on locale, search, account_id, or profile_id beyond the schema, but the source clarification is a meaningful supplement.

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 states a specific verb and resource: it lists audience segments usable for Sponsored Products bid multipliers, including the supported marketplaces. It also distinguishes the tool from sibling tools by explaining that its audience_id values feed ads_update_sp_audience_bidding, while already-applied segments are read via ads_list_sp_campaigns.

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?

It gives explicit usage guidance for the source values: amazon is the default and means Amazon-built audiences, amc means audiences created in Amazon Marketing Cloud, and all combines them. It also describes search as an optional text filter and warns not to invent audience_id values or to report an empty list to the user, leaving little ambiguity about correct use.

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