Call the searchDatabase MCP tool
Search the Reachium people database with human-readable filters: industry/vertical NAMES, locations, title keywords, seniority, company size/type, investor types. Free, read-only: returns the match total and a 10-person sample to refine conversationally before exporting. The result echoes filters_used: for ANY follow-up on the same audience (previews, refinements, exports) pass filters_used back verbatim instead of re-deriving arguments, or counts will shift between turns. Unrecognized names come back in dropped_filters and are IGNORED (the total is then broader than asked; fix and retry); there are no funding-round values (Seed/Series A), and NO family-office investor type; family offices match via company_keyword "family office". Export matches with addSearchToLeadList.
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/searchDatabase
- 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 1 revision of this API.