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

# Call the getBoostingPools MCP tool

`POST /api/v1/actions/getBoostingPools`

## Request

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

List this workspace's boosting pools and its own membership state. Boosting pools are opt-in circles where member LinkedIn accounts automatically like and comment on each other's lead-magnet posts, helping them clear LinkedIn's engagement thresholds. Every workspace has its own internal pool (kind:'workspace', always available, your team only) plus zero or more named partner pools (kind:'pool') this workspace can see: joined (contributing accounts), approved (cleared to join but no accounts added yet), pending (application awaiting review), or available (a public pool you have not applied to). A pool this workspace was rejected from is omitted entirely. Returns members (this workspace's OWN memberships, each with linkedin_accounts identity, daily_boost_limit, boosts_today already used, and is_active), pools (the directory above, with member_count/my_account_count aggregates - rosters never cross a workspace boundary), and stats.boosts_received_today (this workspace's posts boosted today, scoped to pool_id if passed). Pass pool_type and/or pool_id to scope to one pool; omit both for everything. Manage membership with manageBoostingPool.

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
  - `pool_type` 'workspace' | 'named': Restrict members to one pool type.
  - `pool_id` string, uuid: Restrict to one named pool (also scopes stats.boosts_received_today to it).

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