Your agent has an inbox
in four steps.

Returns every inbox the current API key or OAuth token can access. Call this first to discover inbox_id values, so you never copy-paste UUIDs from the dashboard. Each result includes the email address, provider, optional service brand (icloud/yahoo/zoho/yandex/generic/fastmail), and a capabilities object describing which features that inbox supports.

Read, list, and search messages in an inbox. Set action: 'list' for recent message summaries (newest first, with folder/unread filtering and pagination), 'read' for the full content of one message_id (text body, optional sanitized HTML and attachments), 'read_batch' to fetch up to 50 message_ids in one call, 'search' for structured, provider-agnostic filters (from, to, cc, subject, body, text, unread, has_attachment, flagged, since, before), or 'attachment' to download a single attachment (by attachment_index or filename), returned in the MCP-native content block for its type (image/audio/embedded resource) — up to 25 MB. Read-only — never changes anything. The 'search' action is also unlocked on its own by the narrower search:email scope.

Move, copy, flag, or archive messages. Set action: 'move'/'move_batch' (relocate to a destination_folder_id), 'copy'/'copy_batch' (duplicate into a destination_folder_id, leaving the original in place; IMAP, Outlook and Fastmail only), 'flag' (set read/unread/flagged via flag_action on message_ids), 'archive' (move out of the Inbox, non-destructive), or 'search_and_move' (apply to every message matching a structured search, which avoids stale message IDs). Each action needs the scope that matches it: manage:folders for moves and copies, send:email for flag/archive. Deleting messages lives in its own email_delete tool.

Delete messages — its own tool, separate from email_organize, because deleting is destructive. Set action: 'delete'/'delete_batch' (Trash by default, or permanent), or 'search_and_delete' (delete every message matching a structured search — avoids stale message IDs). Deletes go to Trash unless you pass permanent: true, which is irreversible. Every action needs the delete:email scope, and the whole tool is flagged as destructive to your MCP client, which handles user confirmation before anything is removed.

Send new mail or respond to existing messages. Set action: 'send' for a new email (to/subject/body, optional cc/bcc/html_body/reply_to/attachments), 'reply' to answer a message_id (threading headers are set automatically; optional reply_all), or 'forward' a message_id to new recipients (optionally re-attaching the original files). The inbox's signature is appended automatically — on replies and forwards it sits after your text and before the quoted block, governed by the signature's reply mode; pass include_signature: false to suppress it for a single terse message. All three are irreversible once sent.

Manage mailbox folders (labels on Gmail). Set action: 'list' (every folder with its provider-native ID, display name, type, and message counts — use the IDs as the folder argument when listing mail and as a move destination), 'create' (name), 'rename' (folder_id, new_name), or 'delete' (folder_id — irreversible; messages inside may be lost depending on the provider). 'list' needs read:email; create/rename/delete need manage:folders, and delete is flagged as destructive to your MCP client.

Manage draft messages in the inbox's Drafts folder. Set action: 'list' (saved drafts, each with its draft_id, subject, recipients, and created timestamp), 'create' (subject/body required, optional to/cc/bcc/html_body), 'update' (draft_id plus the fields to overwrite), or 'send' (draft_id — removes the draft and sends it, irreversible). The inbox's signature is embedded when the draft is created or updated, so it is already present in the Drafts folder and is not re-appended on send; pass include_signature: false to create a draft without it. On IMAP-backed inboxes a draft_id changes on every update, so always use the latest one; Gmail and Outlook keep a stable draft_id.

Schedule mail for future delivery via a server-side queue. Set action: 'create' (to/subject/body plus a send_at ISO 8601 timestamp — recipients and body are validated immediately, and invalid sends are not queued), 'list' (pending scheduled sends, earliest first, optionally filtered by inbox), or 'cancel' (scheduled_send_id — only sends still 'pending' can be cancelled). The dispatcher runs every minute, so delivery may be up to 60 seconds after send_at.

Find correspondents by name or email with a live scan of your mailbox — there is no stored contact list. Each call scans a recent window of matching mail and returns the people who match, sorted by most-recently-contacted, each with display name, email, matched-message count, and last-contacted timestamp. Counts reflect matched messages in that window, not your full history, and nothing is stored between calls.

Read or configure the inbox's email signature, which is appended server-side on every send, reply, forward, draft, and scheduled message. Set action: 'get' (returns the current signature text and HTML, whether it is enabled, the reply/forward mode, and its source — 'manual', 'gmail_import', or null) or 'set' (write signature_text and/or signature_html, and optionally signature_enabled and signature_reply_mode). Signatures support rich HTML: bold, italic, headings, lists, colors, alignment, links, and hosted logo/images referenced as https URLs, so an agent can set a fully formatted signature by passing signature_html. The same rich editor is available in the dashboard. Setting a signature marks its source as 'manual', which permanently overrides Gmail auto-import for that inbox. 'get' needs read:email; 'set' needs send:email.