Skip to main content
Glama

activation_audience_create

Destructive

Create a new, empty audience on an ad account (ds_id + account_id) to receive an audience activation, e.g. a Meta Custom Audience or a Google Customer Match list. Call activation_audience_list first and call this only when the user asks for a new audience by name: it creates a real object on their ad platform, and Meta allows duplicate names. Returns {id, name}; pass the id in the destination's config via manage_activation_query (FA: audience_id, AW: user_list_id).

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": "<name>"
    },
    "name": "activation_audience_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new audience, as the user wants it shown in the ad platform. Sent as typed: one line, not blank, at most 255 bytes (non-English letters and emoji use more than one).
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.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds real context beyond them: the audience is created empty, it becomes a real object on the ad platform, and duplicate names are permitted (which explains the non-idempotency). It omits permission/auth requirements and any rate limits, so it falls short of 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?

Three sentences, front-loaded with the action and scope, then the conditional guidance, then the return/hand-off. Every clause carries information an agent needs; there is no restatement of the title or filler.

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 non-idempotent, destructive, open-world create tool, the description covers prerequisite check, invocation condition, platform side effects, and the downstream step that consumes the returned id. An output schema exists, and the description still briefly states the return shape, so nothing critical is missing.

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 baseline is 3, but the description adds cross-field meaning the schema does not: ds_id and account_id together identify the destination ('ds_id + account_id'), and the returned id maps to different config keys depending on destination (FA: audience_id, AW: user_list_id). It does not elaborate on the name length/format rule beyond what the schema already states.

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?

Specific verb and resource ('Create a new, empty audience on an ad account'), with the concrete examples (Meta Custom Audience, Google Customer Match list) and the ds_id+account_id scope. It is clearly distinguishable from activation_audience_list, which the description names as the read-side counterpart.

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 prerequisite ('Call activation_audience_list first'), an explicit restriction on when to call ('only when the user asks for a new audience by name'), and the reason to be cautious (real object created, Meta allows duplicate names). It also names the follow-up tool and where the returned id goes.

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