Skip to main content
Glama

activation_audience_list

Read-onlyIdempotent

List the existing audiences on a destination ad account (ds_id + account_id). Works before any audience activation exists. Pass the chosen audience id in a destination's config via manage_activation_query. Read-only; returns {items: [{id, name}], total_count}, unpaginated.

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": {
      "ds_id": "<ds_id>",
      "account_id": "<account_id>"
    },
    "name": "activation_audience_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
ds_idYesDestination data source ID, one marked data_out: true in data_source_discovery (e.g. 'FA').
account_idYesDestination ad account ID from accounts_discovery (e.g. 'act_123456').

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
notesNo
successYes
business_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, but the description adds traits they don't carry: the call is safe to make before any activation exists, results are unpaginated, and the top-level return shape includes a total_count. The unpaginated detail is genuinely useful for an agent deciding whether it needs to loop or page.

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?

Four short sentences, front-loaded with purpose and entirely free of filler. Minor redundancy: it spells out the return object even though an output schema exists and already defines that shape, so that clause earns less than the others.

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?

For a two-parameter read tool, the definition covers what it does, when it applies, what it returns in broad terms, the lack of pagination, and the follow-up call. With an output schema present and annotations carrying the safety profile, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so both ds_id and account_id are already documented in the schema, including discovery pointers to data_source_discovery and accounts_discovery. The description restates the parameter names in parentheses but adds no format or constraint meaning beyond the schema, so the baseline of 3 applies.

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 verb and resource ('List the existing audiences on a destination ad account') plus the exact identifying keys. The clause 'Works before any audience activation exists' separates it from activation_audience_create and the query tools, so an agent can distinguish it without opening siblings.

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?

Gives the condition for use ('works before any audience activation exists') and the downstream step ('pass the chosen audience id in a destination's config via manage_activation_query'), which is a clear workflow cue. It stops short of an explicit when-not statement, e.g. how it differs from activation_audience_create when an audience already exists.

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