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

# Call the updateDraftPost MCP tool

`POST /api/v1/actions/updateDraftPost`

## Request

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

Edit an existing draft/planned/approved/scheduled post: replace the body (content), rename it (topic), and/or move it to a different LinkedIn account (account_id, draft/planned/approved only; unschedulePost a scheduled post first). Pass any combination. Refuses published posts; failed and stuck-publishing posts must go through revertPostToDraft first. Editing a draft/planned/approved post is single-call, no confirmation needed. Editing a SCHEDULED post is two-step: it still auto-publishes to LinkedIn at its existing scheduled time (this never moves that time, only the body that goes out), so the FIRST call (no confirm_token) returns a preview naming the scheduled time and does NOT save anything; call again with the same post_id and content plus confirm_token to actually save the edit.

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
  - `post_id` string, uuid, required
  - `content` string: The full replacement post body (max 3000 characters, the LinkedIn limit). Optional when only changing topic or account_id.
  - `topic` string
  - `account_id` string, uuid: Bind or REASSIGN the publishing account (from getLinkedInAccounts). Works on draft/planned/approved posts; keeps the body, image, and approval.
  - `confirm_token` string: Only needed when editing a SCHEDULED post: from that preview response, resend with the same post_id and content to execute. Not needed for draft/planned/approved edits.

## 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/80c82dd6c7a1?raw)