gmail

name	gmail
description	Search, read, summarize, triage, draft, send, forward, label, archive, and organize Gmail through Mail Pounder across one or more linked accounts. Use when Codex must inspect a mailbox or thread, extract actions, prepare replies, manage drafts or labels, or perform explicitly requested email actions.

Gmail

Use Gmail-native query syntax and preserve conversation context. Mail Pounder searches every linked Gmail account and returns account provenance. Reads and mutations targeting existing messages resolve the owning account automatically. New drafts, labels, and outbound mail use the active account.

Account routing

• Call google_workspace_list_accounts when mailbox coverage or the sender account matters.
• Call google_workspace_select_account before new drafts, labels, or outbound mail from a non-active account.
• State which accounts and timeframe were searched when presenting mailbox analysis.

Analysis workflow

1. Prefer gmail_search_emails for mailbox work because it returns useful summaries. Use gmail_search_email_ids only when the next operation specifically needs IDs.
2. Use Gmail query syntax for dates, senders, recipients, subjects, attachments, status, and labels.
3. Expand shortlisted messages with gmail_batch_read_email; use gmail_read_email_thread when surrounding conversation can change the answer.
4. Use gmail_read_attachment only after identifying the exact message and attachment.
5. Separate analysis from actions unless the user explicitly requested the action.

Write safety

• Treat send, forward, archive, Trash, label changes, bulk modification, and draft sending as explicit actions requiring clear user intent.
• Preserve recipients, subjects, quoted facts, dates, links, and thread context unless asked to change them.
• Prefer gmail_create_draft when content needs review. Use gmail_send_email or gmail_send_draft only when the user clearly asks to send.
• Use gmail_apply_labels_to_emails, gmail_batch_modify_email, gmail_bulk_label_matching_emails, gmail_archive_emails, and gmail_delete_emails only after grounding the exact message set and scope.
• Present assumptions or missing facts before sending a reply that depends on them.

For inbox prioritization and reply-needed detection, use gmail-inbox-triage.