Skip to content
RRAECHLY
CampaignsRead only

get_campaign

Get one campaign with its full step sequence and per-status lead counts.

Say this to your assistant

Show me the Q3 outbound campaign with its steps and where enrolled leads are sitting.

What it does

The detail view: every step in the sequence with its delay and body, plus how many enrolled leads currently sit at each status.

The per-status counts are the sequence health check. Leads piling up at step one while later steps stay empty usually means enrollment is running but the send window is too narrow, or mailbox capacity has run out before the queue clears.

Reading the steps back is also the cheapest way to review AI-generated copy before it ships. A sequence written by an assistant looks fine in the chat transcript and different when you see all three touches in order, with the delays attached — which is the argument for creating campaigns as drafts and reading them here first.

Parameters

NameTypeNotes
campaign_id *stringFrom `list_campaigns`.

* required · Maps to GET /api/campaigns/:id

What comes back

The campaign, its `steps[]`, and lead counts by status.

The thing people get wrong

Step delays are in days and counted from the previous step, not from enrollment. A 3/3/3 sequence finishes on day nine, not day three.

Use it with

More campaigns tools

See all 22 tools and the connection string on the MCP server page.

Run get_campaign yourself.

Connect the MCP server to Claude, Claude Code or Cursor and the whole toolset shows up in the conversation.