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

# Call the getContent MCP tool

`POST /api/v1/actions/getContent`

## Request

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

Read the visitor's LinkedIn content. Call with a `view`: 'pipeline' for status counts and what's waiting/upcoming; 'review' for every draft/approved post awaiting a human, FULL body, oldest first ("what needs my approval"); 'failed' for posts that failed to publish; 'ideas' for recent EXISTING ideas (full hooks; rank 'meh' is default for never-ranked, not a judgment); 'posts' for recent posts with a body preview (optional status filter); 'plan' for the active content plan and cadence; 'brand' for the active brand profile.

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
  - `view` 'pipeline' | 'ideas' | 'posts' | 'plan' | 'brand' | 'review' | 'failed', required: Which slice of the content system to read.
  - `status` 'planned' | 'draft' | 'approved' | 'scheduled' | 'publishing' | 'published' | 'failed': Only for view 'posts': filter by status ('publishing' = a publish attempt in flight, or stuck).
  - `limit` integer: For 'posts' (default 15), 'ideas' (default 10), 'review'/'failed' (default 20).

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