emaillisted

# Gmail -- Best Practices Reference This is the canonical reference for how the Exobrain interacts with Gmail. All skills that scan, read, or draft emails MUST follow these conventions. ## MCP Tools | Tool | Purpose | |------|---------| | `gmail_search_messages` | Search emails with Gmail query syntax | | `gmail_read_message` | Read a specific message by ID | | `gmail_read_thread` | Read a full email thread | | `gmail_create_draft` | Create a draft reply or new email | | `gmail_get_profile` | Get account profile info | | `gmail_list_labels` | List all Gmail labels | | `gmail_list_drafts` | List existing drafts | ## Best Practices ### CRITICAL Rules 1. **Date filtering on every scan.** Always use `after:YYYY/MM/DD` in `gmail_search_messages` queries to scope results. Never scan the full inbox without a date bound. 2. **Read FULL email bodies for job alerts.** Subject lines and snippets are insufficient -- job alert emails (especially LinkedIn) contain multiple listings in the body. Always call `gmail_read_message` on job alert emails to extract all roles. 3. **Actionable items become Things 3 tasks.** When an email requires action (reply needed, decision, follow-up): - Check Things 3 first (`search_todos`) for existing tasks - Create a new task only if no match exists - Include email context in the task notes 4. **No em dashes in outward-facing text.** When composing drafts via `gmail_create_draft`, never use em dashes. Use commas, semicolons, periods, or rew