Skip to main content
Glama

activation_query_status

Read-onlyIdempotent

Get the status of an audience activation: DRAFT, RUNNING, COMPLETED, PARTIALLY_FAILED or FAILED. The cheap check to poll after a run; never returns data rows or config, but includes run-level and per-destination failure reasons when a run fails or partially fails.

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

Input Schema

NameRequiredDescriptionDefault
activation_query_idYesAudience activation id (UUID).

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
notesNo
successYes
business_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: it is a lightweight/cheap call suitable for polling, it deliberately excludes data rows and config, and it surfaces run-level and per-destination failure reasons on failure. It does not discuss rate limits or state transitions, so it lands just below the top.

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?

Two sentences, both front-loaded with the highest-value information (what it returns, then how to use it). The clause about what it does not return is placed exactly where it prevents misuse, and there is no 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?

An output schema exists, so return shape need not be explained; annotations cover the safety profile. For a one-parameter read tool, the description supplies the status vocabulary, the failure-reason behavior, and the polling guidance, leaving nothing an agent needs before calling it.

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?

With a single required parameter at 100% schema description coverage ('Audience activation id (UUID)'), the schema carries the semantics fully. The description adds only indirect meaning by framing the call as something done after a run, which hints the id comes from that run, but it never discusses the parameter itself.

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 (get the status of an audience activation) and immediately enumerates the five possible states (DRAFT, RUNNING, COMPLETED, PARTIALLY_FAILED, FAILED). This makes it trivially distinguishable from the list/run/manage siblings without opening any 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?

'The cheap check to poll after a run' gives an explicit usage context tied to the activation_query_run sibling, and 'never returns data rows or config' implicitly steers the agent elsewhere for actual data. It stops short of naming the alternative tool to use when full results are needed, so it is not a full when/when-not rubric.

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