Skip to main content
Glama

List a campaign's queue

list_campaign_queue
Read-only

Use this when the user wants to review a campaign's messages in one state: waiting for approval (written by AI), scheduled, sent, skipped, declined, or replaced by an edit. status is required. Returns each message's subject, body, time and person; for the next page, send the page's next cursor with the same status and channel. Free.

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": {
      "campaignId": "<campaignId>",
      "status": "<status>"
    },
    "name": "list_campaign_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe `pagination.nextCursor` of the page before. Later pages keep the first page's size.
statusYesThe messages to list: `approval_required` (written by AI, waiting for your approval), `scheduled` (going out at `scheduledAt`), `sent`, `skipped`, `stopped` (declined) or `overwritten` (replaced by an edit).
channelNoOnly the messages of this channel.
pageSizeNoItems per page.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: the fields returned per message (subject, body, time, person), the pagination rule of resending the next cursor with the same status and channel, and a cost note ('Free'). No rate limits or auth requirements are mentioned, but the additions are real.

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 tight sentences: trigger first, required parameter second, return shape and pagination third, with a one-word cost note. Nothing is repeated needlessly and the most decision-relevant information is front-loaded.

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?

For a read-only, closed-world list tool with full schema coverage, the description covers trigger, return fields and pagination well enough to invoke correctly. The only gap is that it never mentions the optional channel or pageSize parameters, which could matter when narrowing a large queue.

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 the enum meanings, cursor semantics, pageSize bounds and campaignId format are already documented in structured data. The description reinforces the status filter and the cursor reuse rule but adds no new meaning for channel or pageSize, so the baseline 3 applies.

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?

The description states a specific verb and resource: review a campaign's messages filtered to one state, and enumerates the states (approval_required, scheduled, sent, skipped, stopped, overwritten). That scope clearly separates it from sibling listing tools such as list_campaign_leads or list_campaign_steps, though it never names an alternative explicitly.

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?

It opens with an explicit trigger: 'Use this when the user wants to review a campaign's messages in one state', and states that status is required, which tells the agent the call cannot be made broadly. There is no when-not guidance or named alternative, so it stops short of a 5.

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