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

# Call the generateIdeas MCP tool

`POST /api/v1/actions/generateIdeas`

## Request

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

Generate 1-10 fresh LinkedIn content ideas of a given type for this workspace. It spends credits per idea (check the balance with getCreditBalance). Use for ideas or inspiration when the user asks what to post about. Returns the new ideas (id, topic, hook). Does NOT draft or publish anything. Call this only to CREATE new ideas; to read existing ideas use getContent with view 'ideas'.

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_type` 'value_post' | 'problem_awareness' | 'personal_story' | 'case_study' | 'authority_boosting', required: The kind of idea to generate.
  - `count` integer: How many ideas (1-10; default 3 unless the user asks for more).
  - `account_id` string, uuid: Optional LinkedIn account UUID to scope the ideas to.

## 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/11682826692b?raw)