list_broadcasts
List broadcasts in the application with status, schedule, and delivery counts. Read-only. Filters combine as AND. Note that delivery counts report messages attempted, not confirmed deliveries. recipientCount is the number of delivery rows once the broadcast has started sending. Before that it is a live count of the audience only when the audience has no filter. null means NOT COMPUTED, never zero: a filtered audience is evaluated when the broadcast sends, and get_broadcast_details reads delivery rows only, so it is null for every broadcast that has none yet. Use get_broadcast_details for one broadcast's full breakdown. To CREATE or SEND a broadcast use apply_actions: create_broadcast makes a draft, update_broadcast (status SCHEDULED) schedules/sends it — see get_action_schema under broadcasts.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. Defaults to 1. | |
| botId | No | Only broadcasts belonging to this bot. Omit for all bots in the application. | |
| limit | No | Broadcasts per page, between 1 and 100. Defaults to 10. | |
| status | No | Only broadcasts in this lifecycle state (FAILED = the send broke and did not finish). Omit for all states. | |
| isRecurring | No | True for recurring broadcasts only, false for one-off only. Omit for both. | |
| applicationId | No | Application (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id. |