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

# Call the draftPost MCP tool

`POST /api/v1/actions/draftPost`

## Request

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

Draft a LinkedIn post from a topic with the house copywriting engine, grounded in the brand profile. It spends credits (check the balance with getCreditBalance). Creates a DRAFT only: it never schedules or publishes. Returns post_id, the draft body and the artifact ids of the editable copy (read or revise them with getArtifact / updateArtifact, sending back the version you read). Pass post_id to draft INTO an existing planned slot from generatePlan instead of creating a new post; hook steers the angle; account_id attributes the draft. Edit with updateDraftPost, approve with approvePost, schedule with schedulePost.

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
  - `topic` string: What the post should be about, in a sentence or two. Required when creating a new draft; optional when drafting into an existing planned slot via post_id (topic can come from the slot).
  - `hook` string: Optional angle/hook direction for the post.
  - `account_id` string, uuid: Optional LinkedIn account UUID to attribute the draft to (use one returned by getLinkedInAccounts). Omit if unknown.
  - `idea_id` string, uuid: Optional: an existing idea id from getContent or generateIdeas to draft from.
  - `post_id` string, uuid: Draft into an EXISTING planned slot (from generatePlan / the calendar) instead of creating a new ad-hoc draft. Omit for a normal new draft.

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