Call the getLeadLists MCP tool
List the workspace's lead lists with name and lead count. Call BEFORE createDraftCampaign so the user picks a real list. Four ways to build a list over MCP: (1) find NEW leads on LinkedIn: getPlaybook("lead_gen") then startScrape (launch scope; without it, send the user to https://app.reachium.io/scraper); (2) pull from the Reachium database: searchDatabase then addSearchToLeadList (write scope, charges credits); (3) import the user's own CSV: createLeadList then importLeads (write scope); (4) filter an existing list to FREE-InMail-able open profiles, or merge lists together: manageLeadList (write scope). Workspace-wide lead counts: getLeadStats.
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.
Request
- Base URL: https://app.reachium.io
- URL: https://app.reachium.io/api/v1/actions/getLeadLists
- Auth: HTTP bearer
Headers
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
Response
The result of calling this tool.
Changes
No recorded changes to this operation across all 2 revisions of this API.