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

# Call the generateCampaignCopy MCP tool

`POST /api/v1/actions/generateCampaignCopy`

## Request

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

Generate the campaign message copy (message 1 sent after connection is accepted, plus a follow-up message 2) using the brand-aware engine. Call this AFTER you know the goal, the target persona, and the brand (via getBrandProfile, or pass company_name/offer inline). Show the returned copy to the user for approval before creating the draft with createDraftCampaign. Writes copy only; it creates no campaign. Pass mode:"inmail" to instead write a cold InMail subject line + body.

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
  - `approach` string, required: The campaign goal/angle (e.g. "book intro calls").
  - `icp` string, required: The chosen target persona / who we are targeting.
  - `proof_point` string: A concrete result or number, if known.
  - `company_name` string: Override: sender company, when no saved brand.
  - `offer` string: Override: what they do/sell, when no saved brand.
  - `tone` string: Override: tone of voice, when no saved brand.
  - `follow_up_style` string: Optional follow-up style for message 2.
  - `mode` 'outreach' | 'inmail': Copy mode. "outreach" (default) = message 1 (after connection accepted) + follow-up message 2. "inmail" = a COLD InMail subject line + body for people the sender is NOT connected to (permission-based first touch). Use "inmail" ONLY when the campaign uses a Send InMail step.

## 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)