create_warmup_pool_account
Add a real inbox you control that receives warmup mail and replies to it.
›Add my personal Gmail as a warmup pool account with a daily target of 8.
What it does
Warmup needs somewhere to send. A pool account is a real inbox under your control — typically a Gmail or Outlook address — that receives warmup messages and replies to them, generating the two-way conversation that builds sending history.
This is the part of warmup most platforms hide inside a shared network. Running your own pool means you can see both ends of every thread, which is what makes the reply counts in `warmup_stats` trustworthy rather than a number on a dashboard you have no way to audit.
At least one active pool account is required before warmup can do anything. `daily_target` bounds how much warmup mail any single inbox absorbs per day.
Parameters
| Name | Type | Notes |
|---|---|---|
| email * | string | A real inbox you control. |
| label | string | Human-readable name for the pool entry. |
| provider | string | gmail | outlook | other. Defaults to gmail. |
| daily_target | integer | Max warmup mails this inbox receives per day. Defaults to 5. |
* required · Maps to POST /api/warmup/accounts
What comes back
The created pool account.
The thing people get wrong
Use inboxes you genuinely control and check. A pool account that silently stops accepting mail turns your warmup metrics into fiction.
Use it with
More warmup tools
See all 22 tools and the connection string on the MCP server page.