list_activity
Read the send log: recipient, mailbox, subject, sent or failed, and the error.
›Show me every failed send in the last run, grouped by error, and tell me what is causing them.
What it does
The last 100 send attempts with recipient, sending mailbox, subject, outcome and — when something failed — the actual error string rather than a generic status.
Optionally filtered by campaign. Because the errors are surfaced verbatim, this is where deliverability debugging actually happens: a rejected recipient, a throttle, or an SES-level refusal each read differently, and your assistant can group them and tell you which one you have.
Pair it with `trigger_send` for a tight loop: fire the pipeline, read the log, fix, repeat.
It is worth reading even when nothing looks broken. A steady trickle of the same failure across many recipients is the signature of a list problem rather than an infrastructure one, and it is invisible in aggregate success rates until it is large enough to have already cost you something.
Parameters
| Name | Type | Notes |
|---|---|---|
| campaign_id | string | Filter to a single campaign. |
* required · Maps to GET /api/activity
What comes back
Up to 100 recent send-log entries with outcome and error detail.
The thing people get wrong
Sent means accepted by SES for delivery, not delivered to an inbox. Bounces and complaints arrive later over the webhook and land on the lead record.
Use it with
More pipeline tools
See all 22 tools and the connection string on the MCP server page.