Call the getCampaigns MCP tool

List the workspace's campaigns, paginated: up to 100 per page (default 20) with total, has_more, and next_cursor (pass it back as cursor), plus status and type filters. Lead-magnet rows carry a lead_magnet block (keyword, document id + title, hook post, armed, sender_resolution) so a funnel audit is one call; getCampaignSequence reads one campaign's full copy. Outreach campaigns carry ALL-TIME stats since launch (active leads, requests, acceptance/reply rate, bookings); lead-magnet campaigns carry lm_stats instead (captured, DMs, replies, bookings); retargeting/re_engagement campaigns carry re_stats instead (enrolled, messaged, replied, positive, booked - no requests/accepted); pure-InMail campaigns (a send_inmail step with no connection_request) carry inmail_stats instead (sent, replies, open-profile rate, skip reasons - always all-time). For date-windowed numbers (for example "last week"), use getWorkspaceStats or getCampaignFunnel with days_back instead of these lifetime totals. Use getCampaignStats for one named campaign, getCampaignFunnel for stage-by-stage conversion. For workspace-wide totals, use getWorkspaceStats (optionally with days_back) instead of aggregating this page, or point to https://app.reachium.io/campaigns.

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.