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

# Call the findLeads MCP tool

`POST /api/v1/actions/findLeads`

## Request

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

Find specific leads in the workspace: by name or LinkedIn URL (query), by lead list (list_id from getLeadLists), by status, by tag, or by outreach_status (replied | booked | contacted | closed). Returns per-lead identity, status, tags and notes, paginated with a total. Result order is not part of the contract and varies by filter mode; page with offset/limit for full coverage. For aggregate counts use getLeadStats. To edit a lead found here, pass its lead_id to updateLead.

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
  - `query` string: Name fragment, full name ("John Smith": words match across name fields in any order), or LinkedIn URL fragment.
  - `list_id` string, uuid: Restrict to one lead list (id from getLeadLists).
  - `status` 'new' | 'active' | 'contacted' | 'qualified' | 'lost' | 'unsubscribed'
  - `outreach_status` 'booked' | 'replied' | 'closed' | 'contacted': replied = lead answered; booked = meeting booked.
  - `tag` 'positive_reply' | 'not_a_fit' | 'booked_in' | 'no_engagement' | 'off_platform_activity' | 'follow_up_later' | 'do_not_contact' | 'customer'
  - `limit` integer: Rows per page (default 20, max 100).
  - `offset` integer

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