Skip to main content
Glama

activation_query_list

Read-onlyIdempotent

List your audience activations, or read specific ones by passing their ids; never returns data rows. Use it to recover an activation_query_id, or to check an activation's ready_to_run and missing before running it. total_count counts every match, not just this page.

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

Input Schema

NameRequiredDescriptionDefault
idsNoactivation_query_id values to read, at most 100. Omit to list all. Unknown ids are left out of items, not an error.
limitNoPage size, 1-1000. Default 100.
stateNoOnly return activations in this state: DRAFT, RUNNING, COMPLETED, PARTIALLY_FAILED or FAILED.
offsetNoNumber of activations to skip. Default 0.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
notesNo
successYes
business_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description only needs to add context beyond them — and it does: it discloses that no data rows are ever returned and that total_count counts all matches rather than the page. Pagination-result semantics are the kind of behavioral detail annotations cannot express.

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?

One dense sentence that front-loads the primary purpose, then the secondary use case, then the result-count caveat. Every clause carries useful information, though the semicolon stacking makes it slightly harder to scan than a two-sentence split would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need not be re-explained, and the description still flags the two fields most likely to drive a next action (ready_to_run, missing) plus pagination counting behavior. Complete for a read-only list/read hybrid; only the absence of explicit sibling routing keeps it from full marks.

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%, so ids, limit, state, and offset are already documented in the schema, including the 'unknown ids are left out, not an error' nuance. The description adds no syntax or semantics for the parameters themselves; the only numeric detail it mentions (total_count) is a return value, not an input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List your audience activations') and distinguishes two modes of operation: listing versus reading specific records by id. It also declares the key scope boundary ('never returns data rows'), which separates it from query-execution tools, but it never names a concrete sibling to route away from.

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 a clear when-to-use rule: recover an activation_query_id, or check ready_to_run and missing before running an activation. That implicitly points to the run tool as the follow-on step. No explicit 'do not use this for X, use Y instead' exclusion is given, so it stops short of full alternative routing.

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