| name | gmail-inbox-triage |
| description | Triage Gmail across linked accounts into urgent, needs-reply-soon, waiting, and FYI buckets through Mail Pounder. Use when Codex must rank inbox attention, detect unanswered conversations, distinguish client or external follow-ups from noise, or produce an Inbox Zero-style action list. |
Gmail Inbox Triage
Build on gmail. Treat reply-needed and urgency as evidence-based inferences, not guaranteed mailbox states.
Workflow
- Call
google_workspace_list_accounts and state the accounts covered when the user asks for cross-account triage.
- Default to
INBOX and a clear recent timeframe unless the user asks for a broader audit.
- Use
gmail_search_emails to shortlist messages. Exclude newsletters, calendar churn, transactional mail, and automated alerts when they dominate the results.
- Use
gmail_batch_read_email when snippets are insufficient.
- Use
gmail_read_email_thread for active conversations, reply-state judgments, or any case where the surrounding thread may change the classification.
- Return explicit buckets:
Urgent: time-sensitive direct asks, blockers, or deadline-bound decisions.
Needs reply soon: direct asks, client or external follow-ups, and active conversations where the user appears to owe the next response.
Waiting: the user already replied or another party owns the blocker.
FYI: announcements and low-action informational mail.
Include account, sender, subject, reason, evidence, and likely next action for every item. State timeframe, query scope, exclusions, and confidence. Do not claim the inbox is fully triaged when the scan was narrow.