Actions

Call the listIcps MCP tool

Changed on

List the ICPs (ideal customer profiles) on the active brand profile: name, priority, status, titles to include and exclude, seniority, functions, headcount bands, industries, geographies, stage, triggers, pains, verbatim phrases, desired outcome, fit rules (must-have, should-have, disqualifiers) and whether those rules are confirmed. Read before building a list, writing copy for a specific audience, or proposing ICP changes with upsertIcp. The legacy icp section of getBrandProfile is a cache of these rows.

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.

post/api/v1/actions/listIcps

Request

  • Base URL: https://app.reachium.io
  • URL: https://app.reachium.io/api/v1/actions/listIcps
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Optional caller-generated key (8-200 characters: letters, digits, dot, underscore, colon, or hyphen). A final tool result is replayed for the same key and body. An ambiguous result remains 409 under that key; reconcile external state before using a new key. Reuse with a different body returns 422.

Request body

object required

Response

The result of calling this tool.

dataunknown required
errorunknown required

Changes