Skip to main content
Glama

manage_activation_query

Destructive

Create or update an audience activation: the source data to pull, which fields are email or phone identifiers, and optional destinations. Omit activation_query_id to create; provide it to update. On update, send only the parts that change: an omitted source or destinations is kept, but a source or destinations list you send replaces the stored one and must be complete ([] removes all destinations). Returns its state (activation_query_id, ready_to_run, missing). Saving stores configuration only and reads or sends no records; identifiers are SHA-256 hashed before upload, and sending happens only in a separate run step the user confirms. Discover source/accounts/fields with the data_source_discovery, accounts_discovery, and field_discovery tools first, and each destination's audience with activation_audience_list. A source that needs connector settings (e.g. BigQuery's date_column) takes them in source.settings. Confirm the setup with the user before saving. For a Google Ads (AW) destination, show the user this notice verbatim before setting its terms acceptance and consent, and set them only from their answer, never on your own: "By setting the consent status to "granted", you confirm on behalf of the organisation you represent that it complies with Google's Customer Match Policy and, for any end users in the EEA, UK or Switzerland in this audience, that it has provided all required notices and obtained valid consent to the sharing of their data with Google for advertising and ad personalization, as required by applicable law and Google's EU User Consent Policy. You instruct Supermetrics to send this consent status to Google, and Supermetrics relies on this confirmation."

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": "manage_activation_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoThe source data to pull plus its identifier mapping. Required on create. On update, omit it to keep the stored source, or send it complete to replace it. If data_source_discovery reports is_date_range_required, pass a date range (a relative one such as last_30_days is re-evaluated on every run). BigQuery (BQ2) needs settings={'date_column': '<column>'} and a date range; only rows whose date falls in the range are included. A run sends at most a capped number of source rows (50,000 by default); rows past the cap are not delivered.
destinationsNoOptional destination instances. On update, the list sent replaces the stored one; omit it to keep them.
activation_query_idNoAudience activation id. Omit to create a new one; provide it to update an existing one.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
notesNo
successYes
business_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that saving is configuration-only with no reads or sends, that identifiers are SHA-256 hashed before upload, that delivery happens in a separate user-confirmed run step, that omitted fields are preserved while sent lists are replaced, and that runs cap at 50,000 source rows. The legal notice requirement for AW destinations is a genuinely non-obvious behavioral obligation.

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?

Front-loaded with the create/update decision, then prerequisites, then the compliance notice — a sensible order. The verbatim AW legal text is bulky but mandatory for correct use, while a few clauses (settings example, cap detail) repeat schema content and could be trimmed.

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?

Covers the full lifecycle an agent needs: discovery prerequisites, update replacement semantics, hashing/no-send behavior, and the compliance gate. An output schema exists and is summarized (activation_query_id, ready_to_run, missing), so return-value explanation is appropriately left out.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond the schema: replace-vs-keep semantics for source and destinations, the note that relative date ranges re-evaluate each run, the connector settings requirement for BigQuery, and the row cap. Some of this duplicates schema prose (identifiers mapping, settings keys), so it falls short of a full 5.

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+resource pair ('Create or update an audience activation') and immediately enumerates what the resource contains (source data, identifier fields, optional destinations). It is clearly distinguished from siblings by naming activation_query_run as the separate execution step and the discovery tools as prerequisites.

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 routing rules: omit activation_query_id to create, provide it to update, and on update send only changed parts because a sent source/destinations list replaces the stored one. It also names which tools to call first (data_source_discovery, accounts_discovery, field_discovery, activation_audience_list) and requires user confirmation before saving.

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