---
title: "Call the getCampaignStats MCP tool"
method: POST
path: "/api/v1/actions/getCampaignStats"
tags: ["Actions"]
---

# Call the getCampaignStats MCP tool

`POST /api/v1/actions/getCampaignStats`

## Request

- Base URL: `https://app.reachium.io`
- URL: `https://app.reachium.io/api/v1/actions/getCampaignStats`
- Auth: HTTP bearer

Find campaigns by name substring (case-insensitive) and return their stats. Returns UP TO 3 best matches: match_count counts THIS search's matches (max 3), NOT the workspace total. Stats default to ALL-TIME totals since launch; pass days_back (1-365) to window them instead. Shape depends on campaign type/sequence: lead-magnet campaigns return lm_stats (captured / DMs / replies / booked) instead of outreach rates; retargeting/re_engagement campaigns return re_stats (enrolled / messaged / replied / positive / booked - no requests/accepted; messaged also counts a lead who messaged in first, before their drip fired); pure-InMail campaigns (a send_inmail step with no connection_request) return inmail_stats (sent / replies / open-profile rate / skip reasons), always all-time regardless of days_back. booking_rate = meetings booked / positive replies for outreach and retargeting campaigns, and meetings booked / replies for lead-magnet campaigns; the InMail shape has no booking_rate or meetings_booked field at all. Use when the user names a SPECIFIC campaign; use getCampaigns for overviews. If the campaign runs an A/B split, the result includes per-variant contacted/accepted/replied - narrate which arm leads and whether the sample is big enough to trust; the A/B block always stays all-time regardless of days_back.

Called through the Actions bridge: the response is that tool's own result, wrapped as `{ data: <tool result> }` under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE `data`, never remapped to an HTTP status (see the templated `/api/v1/actions/{toolName}` operation above for the full protocol, and `x-mcp-actions` for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `name` string, required: A substring of the campaign name to search for (case-insensitive). E.g. "lead magnet" or "Q1".
  - `days_back` integer: Window the stats to the last N days. Omit for all-time.

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

---

[API](https://skmtc.dev/reachium/apis/reachium-api.md) · [All operations](https://skmtc.dev/reachium/apis/reachium-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reachium/apis/reachium-api/revisions/30c16b30b499?raw)