check_reply_capture
Why an outbound SES mailbox can or can't send: for each one (or mailbox_id), whether its replies reach Raechly and, when they don't, a title, the reason, recommended steps in order (each with an action: open a link, setup = reconcile_reply_capture, check = this tool again, connect = connect_mailbox with an app password (username = the account that owns an alias), add_domain = create_domain, product_email = set_mailbox_purpose lifecycle) and alternatives, most likely first.
What it does
Why an outbound SES mailbox can or can't send: for each one (or mailbox_id), whether its replies reach Raechly and, when they don't, a title, the reason, recommended steps in order (each with an action: open a link, setup = reconcile_reply_capture, check = this tool again, connect = connect_mailbox with an app password (username = the account that owns an alias), add_domain = create_domain, product_email = set_mailbox_purpose lifecycle) and alternatives, most likely first. Addresses like hello@ or a product's name on a company domain are usually product email, which needs no capture: ask before treating them as cold-email senders. The advice already accounts for where the domain's DNS is (dns_host) and who receives its email (mail_host): present the recommended steps first. Never suggest turning on Cloudflare Email Routing for a domain whose email is handled elsewhere; that stops its email arriving. Product-email (lifecycle) mailboxes don't need capture and aren't listed. Read-only.
Parameters
| Name | Type | Notes |
|---|---|---|
| mailbox_id | string | Only this mailbox |
* required
More mailboxes tools
See all 147 tools and the connection string on the MCP server page.