List every inbox (mailbox or account) this API key may use. Call it FIRST for the inbox_id the other tools take. Each entry carries the UUID, email address, display name, provider, optional service brand (icloud/yahoo/zoho/yandex/generic) and a capabilities object.

Read, list and search email in one inbox. list and search return a single page: when the response says has_more, call again with the returned next_offset and otherwise identical arguments. Only has_more: false means you have seen everything. Long bodies are windowed the same way: body_truncated means read again with body_next_offset as body_offset.

Move, copy, flag or archive messages in one inbox. Get message ids from email_read first. On Gmail a move adds the destination label and removes INBOX, leaving other labels in place. Needs manage:folders; deleting is the separate email_delete tool.

Delete messages in one inbox. Flagged DESTRUCTIVE so your MCP client can ask for confirmation first. Deleted mail goes to Trash and stays recoverable unless you pass permanent: true, which is irreversible. Needs the delete:email scope.

Send new mail, reply, or forward from one inbox. The inbox's signature is appended automatically, above the quoted text on replies and forwards; pass include_signature: false to suppress it.

Manage mailbox folders, which are labels on Gmail: the arguments say 'folder' for cross-provider compatibility, but Gmail returns and manages labels (type: 'label'). 'list' needs read:email, the rest manage:folders.

Manage unsent drafts in one inbox. On IMAP a draft_id changes on every update, so always use the most recent one. The signature is embedded on create and update (include_signature: false to skip) and 'send' transmits the stored body as-is, so it is never doubled. 'reply' also needs read:email, 'send' needs send:email.

Queue mail for later delivery, and manage what is queued.

Read or set an inbox's signature, which the server appends on send/reply/forward/draft/scheduled mail. Setting one marks the source 'manual', which overrides Gmail auto-import. 'get' needs read:email, 'set' needs send:email.

Create and manage unattended scheduled triage rules. A rule is a stored search plus one fixed action, evaluated on a cadence with NO model in the loop: mail is matched, never interpreted. Set action: 'create' (name, filter, rule_action, interval_minutes; the rule is created DISABLED), 'list', 'get' (automation_id), 'update' (automation_id + fields), 'enable'/'disable' (automation_id), 'delete' (automation_id; run history is kept), 'runs' (automation_id, recent run counters), or 'preview' (DRY RUN: reports what a filter matches right now and applies nothing). NOTE the two different keys: action selects the operation on this tool, while rule_action is the action the RULE performs on matching mail. Rule actions are move, label (applied as a Gmail label, an Outlook category or an IMAP keyword), mark_read, forward and draft_reply. DELETING MAIL IS NOT AVAILABLE to an automation. A forward is ALWAYS held for human approval whatever the inbox's approval setting says, and a draft_reply only ever writes a draft. Always 'preview' before you 'enable'. Every action needs manage:automations.

Find people by name or email fragment. There is no stored contact list: each call runs a bounded, header-only scan of a RECENT window of matching mail, so message_count counts matches inside that window, not an all-time total. Returns display name, address, count and last-contacted time, most recent first. For general or cross-inbox questions ('who do I email most about X?') OMIT inbox_id so every accessible inbox is scanned.

Fetch the full contents of a send that is waiting for human approval, including its body, so it can be shown in the review card. Read-only. Approving is not possible from here: it requires the signed-in review page linked as review_url.

Reject a send that is waiting for human approval, so it is never delivered. decision accepts only "reject". Approving is deliberately not available over MCP — it requires a signed-in browser session with an owner or admin role, at the review_url of the approval.

Change the subject or body of a send that is waiting for human approval. The message still has to be approved afterwards, and the reviewer sees the edited version. Subject can only be set on operations that carry one (email_send, schedule_create).

Set the delivery time of a send that is waiting for human approval. Nothing is queued until it is approved; this only decides when an approved message goes out. send_at must be in the future.

Run a bulk delete or move that was previewed as a plan. Takes only the plan_id: which messages are affected was decided and frozen when the preview was created, and cannot be changed here. A plan runs at most once and expires 15 minutes after it is created.

Decline a previewed bulk delete or move, so it can never run. Takes only the plan_id. Nothing in the mailbox changes. A preview would also expire on its own after 15 minutes; cancelling records the decision instead of leaving it implicit.