Skip to main content
Glama

List campaigns

list_campaigns
Read-only

Use this when the user asks which campaigns exist or how they are doing. Returns the organization's campaigns with what each has done: people enrolled, messages sent by kind, and opens, clicks, replies and positive replies as a count and a share of messages sent. Narrow them with status, type or search; for the next page, send the page's next cursor with the same filters. Free.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly campaigns of this type.
cursorNoThe `pagination.nextCursor` of the page before. Later pages keep the first page's size.
searchNoOnly campaigns whose name contains this text, in any case.
statusNoOnly campaigns in this state: `initializing` (a draft), `active`, `completed` (running, with nothing left to send), `stopped`, `paused_manual` or `initialization_failed`.
pageSizeNoItems per page.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description still adds non-obvious behavior: the call is 'Free' (no cost/credit impact) and later pages retain the first page's size while requiring the same filters — both are operational facts an agent would otherwise have to guess.

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 sentences, front-loaded with the trigger, then the return shape, then the filtering/pagination mechanics, closing with the single-word 'Free.' No filler and nothing repeated from the schema verbatim.

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?

There is no output schema, and the description compensates by spelling out the returned metrics and their count/share form. With five optional parameters fully covered by the schema and safety semantics covered by annotations, an agent has everything needed to call it correctly and interpret the result.

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 100%, so the baseline is 3 and the schema already documents every filter and enum value. The description contributes beyond that by framing the filters as a combinable narrowing set and by noting the cursor must be sent 'with the same filters', a usage constraint the schema's cursor text does not state.

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?

The description states a specific verb and resource ('Returns the organization's campaigns') and enumerates the exact payload: people enrolled, messages sent by kind, and opens/clicks/replies as both count and share. That enumeration distinguishes it from the campaign sub-resource siblings such as list_campaign_leads, list_campaign_steps, and list_campaign_queue without needing to name them.

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 gives a concrete trigger ('when the user asks which campaigns exist or how they are doing') and explains how to narrow with status/type/search and how to paginate. It stops short of explicit exclusions or naming an alternative tool for campaign-level versus lead-level questions, so it is clear context rather than full when/when-not 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