Search and triage all your mailboxes; draft replies and campaigns; send only as you allow.
Scored across 17 tools
Most tools target a distinct resource+action (archive/move/trash/restore are distinguished by their explicit destinations and reversibility), and the list_* family separates campaigns, drafts, folders, contacts and inbound email clearly. The main soft spots are send_reply vs draft_reply (send_reply can itself produce a draft depending on the user's BumbleBox setting) and list_to_answer vs list_replies_to_validate, which require careful reading of the descriptions to separate.
All names are snake_case and verb-first (archive_email, list_folders, search_emails, update_campaign_draft), which makes the set predictable. Minor deviations like draft_reply (verb reused as noun elsewhere) and restore_to_inbox break the strict verb_noun shape but remain readable.
17 tools sit in the upper-but-reasonable band for an email plus prospection domain, and each has a defensible role. A couple of the listing tools (list_replies_to_validate, list_to_answer) could arguably be filters rather than separate tools, but nothing is duplicative filler.
Inbound email handling is well covered (read, search, move/archive/trash, restore, reply), but the campaign side is half-open: drafts and missions can be read and drafts written/updated, yet there is no way to create a campaign or a mission, and no explicit campaign-read tool. There is also no operation to compose a brand-new outbound email or handle attachments, which are notable gaps an agent will hit.
Moves one inbox email to its mailbox's archive folder, on the mail server too. Undone by restore_to_inbox. Nothing is deleted.
Inputs: email_id (required). Returns: moved
Writes one draft inside an existing campaign, to one recipient (added to the campaign list if new), from the campaign's sender. Nothing is sent: the draft waits for the user to validate the campaign send in BumbleBox.
Inputs: to (required), body (required), subject (required), mission_id (required), +1 more. Returns: draft
Saves the text as the reply draft of a received email, from the address the email was written to (a brand address or the mailbox). needsIdentity: that address cannot send until the user verifies it in BumbleBox. Nothing is sent: the draft waits in BumbleBox (Pilotage › prepared replies) until the user reviews it and clicks Send. Saving again replaces the previous draft of the same email.
Inputs: body (required), email_id (required), subject. Returns: draft
One email in full: sender, recipients, date, subject, plain-text body, attachment names, folder and BumbleBox classification.
Inputs: id (required). Returns: email
Events of the connected Google calendars between two dates (default: the next 7 days, at most 62 days).
Inputs: to, from. Returns: events
The drafts of one campaign that wait for the user to validate them in BumbleBox (recipient, subject, plain-text body, sender), newest first, with the true totals.
Inputs: mission_id (required), limit. Returns: counts, drafts
The folders of each connected mailbox, as last synced. Trash, spam, sent and drafts are left out.
Inputs: no named parameters. Returns: mailboxes
The user's prospection campaigns (missions), most recently active first, with the number of drafts waiting, emails sent and prospects who replied.
Inputs: limit. Returns: missions
Replies received on campaigns that still need the user: prepared reply drafts waiting for validation, and replies with no answer yet (with the stored AI triage: kind, summary, whether a human is needed).
Inputs: no named parameters. Returns: drafts, pending
Received emails BumbleBox classified as needing a reply and still in the inbox, newest first.
Inputs: limit. Returns: emails
Moves one inbox email to an existing folder of the same mailbox (see list_folders), on the mail server too. No folder is created. Undone by restore_to_inbox.
Inputs: folder (required), email_id (required). Returns: moved
Moves an archived, filed or trashed email back to the inbox, on the mail server too.
Inputs: email_id (required). Returns: email_id, restored
Contacts BumbleBox knows from the mail history (name, address, organization domain, exchange counts, last exchanges, VIP mark, note), matched on name, address or domain.
Inputs: limit, query. Returns: contacts
Searches every connected mailbox (sender, subject, preview), newest first. Operators: from:, subject:, before:YYYY-MM-DD, after:YYYY-MM-DD, in:sent (only what the user sent, from any mailbox or alias); the rest is free text. Deleted emails are not returned.
Inputs: query (required), limit. Returns: results
Replies to the sender of one received email, and only to them (no Cc, no Bcc, no attachment), from the address the email was written to. What happens next is the level the user set in BumbleBox for this kind of reply: a draft, a reply waiting for one tap (the default), or a reply that leaves after a delay the user can cancel. Anything that commits the user (amounts, bank details, acceptance, contracts, dates, links) always waits for the user, and so does a reply from an address the user has not verified (needsIdentity). The result says which one applied.
Inputs: body (required), email_id (required). Returns: reply
Moves one inbox email to its mailbox's trash when BumbleBox certifies it as noise (spam, newsletter, promotion, with a unanimous safety vote and no known contact or action word). Any other email is not moved: it becomes a proposal the user confirms in one tap in BumbleBox. Never a permanent deletion; undone by restore_to_inbox.
Inputs: email_id (required), reason. Returns: result
Changes the subject, body or recipient of a draft that is still a draft. Nothing is sent, and a draft the user already validated cannot be changed.
Inputs: draft_id (required), mission_id (required), to, body, +1 more. Returns: draft
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
One inbox for all your addresses: your AI agent reads, sorts, drafts and sends with your permission.
Read, search and draft replies across all your mailboxes, Google Chat and Telegram.
Read, organise and send from your existing email accounts. Nothing sends without your approval.
Let your agent handle your email, on your terms. Reads what you allow, replies with your OK.
Add one secure layer between your agents and this server.
