Google Email

Available Tools

Use these MCP tools for all Gmail operations. Authentication is handled automatically.

gmail_list_messages

List messages in the inbox. Returns message IDs — use gmail_get_message to fetch details.

• max_results (optional): Number of messages (default 20, max 100)
• page_token (optional): For pagination
• query (optional): Gmail search syntax (e.g., is:unread, from:[email protected])

gmail_get_message

Get full message details including headers, decoded body text, and labels.

• message_id (required): The Gmail message ID
• format (optional): full (default) or metadata (headers only, faster)

Returns parsed fields: from, to, subject, date, messageId, inReplyTo, body.

gmail_search_messages

Search Gmail with query syntax. Returns matching message IDs.

• query (required): Gmail search query (e.g., from:alice subject:report after:2026/03/01)
• max_results (optional): Max results (default 20)

gmail_modify_labels

Modify labels on a message. Common operations:

• Archive: remove_labels: ["INBOX"]

• Mark read: remove_labels: ["UNREAD"]

• Archive + mark read: remove_labels: ["INBOX", "UNREAD"]

• message_id (required): The message ID

• add_labels (optional): Label IDs to add (e.g., ["STARRED", "IMPORTANT"])

• remove_labels (optional): Label IDs to remove

gmail_create_draft

Create a Gmail draft. The user must review and send it in Gmail.

• to (required): Recipient email addresses
• subject (required): Subject line (prefix with Re: for replies)
• body (required): Plain text body
• cc (optional): CC recipients
• bcc (optional): BCC recipients
• in_reply_to (optional): Message-ID for threading replies
• references (optional): References header for threading
• thread_id (optional): Gmail thread ID to keep reply in same thread
• html_body (optional): HTML version (creates multipart message)

Returns the draft ID and a Gmail deep link for the user to review.

Draft Best Practices

1. Always provide the Gmail deep link after creating a draft so the user can review and send.
2. Summarize the draft before creating — show To, Subject, and a brief preview. Ask for confirmation unless the user gave explicit instructions.
3. Never auto-send — always create drafts, never send directly.
4. Preserve threading — when replying, always include in_reply_to, references, and thread_id.

Email Triage Workflow

When triggered for triage (wakeup reason: email_triage):

1. Fetch new messages using gmail_list_messages with query: "is:unread"
2. Fetch calendar context — if the google-calendar skill is also installed, use gcal_list_events for the next 24 hours before triaging
3. Get details for each new message with gmail_get_message
4. Classify each message: urgent, actionable, or informational
5. Cross-reference with calendar — note connections between emails and upcoming events
6. For actionable messages: Create tasks describing the action needed
7. Draft replies for messages with clear responses
8. Post triage summary to the chat thread
9. Archive processed messages with gmail_modify_labels