Skip to main content
Glama

activation_query_run

Destructive

Run an audience activation: hash its email and phone identifiers and upload them to every destination. Irreversible. For an activation whose ready_to_run is true. Returns state RUNNING at once; the run goes on in the background, so follow it with activation_query_status.

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": {
      "activation_query_id": "<activation_query_id>"
    },
    "name": "activation_query_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
activation_query_idYesThe audience activation to run, as returned by manage_activation_query.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
notesNo
successYes
business_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive, non-idempotent, non-readonly, open-world, but the description adds material context they don't cover: exactly what data leaves the system (hashed email/phone identifiers), that it fans out to every destination, that the action is irreversible, and that the call returns immediately with state RUNNING while work continues in the background.

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?

Four short sentences, front-loaded with the action, then the irreversibility warning, the precondition, and the async follow-up. No filler or restatement of the tool name.

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 one-parameter destructive async operation, the description covers the action, the irreversible side effect, the precondition, the immediate return value, and the polling path. An output schema exists, so return-shape detail is correctly left out.

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 description coverage is 100% and the single parameter already says it is 'the audience activation to run, as returned by manage_activation_query.' The description adds only the readiness requirement on that activation, which is modest extra meaning beyond the schema — baseline 3 is appropriate.

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 (run) and resource (audience activation), then spells out the two underlying actions — hashing email/phone identifiers and uploading to every destination — which is far more informative than the title. An agent can distinguish this from activation_query_status or activation_query_list without opening a schema.

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 an explicit precondition ('for an activation whose ready_to_run is true') and names the follow-up tool to call after launch ('follow it with activation_query_status'). It lacks an explicit when-not clause (e.g. avoid re-running an already-RUNNING activation), so it falls just short of the top band.

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