gmail-mcp-work-with
Key gotchas and practical tips for using Gmail MCP, based on real usage experience
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Key gotchas and practical tips for using Gmail MCP, based on real usage experience
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Helps users connect and use a service in Rebel when it isn't already in the built-in connector catalog. Acts as an expert advisor — runs the full build-vs-buy check (catalog, MCP Registry, community) before scaffolding a custom MCP server and guiding research, implementation, security review, and contribution.
Add, update, or remove connectors (MCP servers) in Rebel. Searches the built-in connector catalog first before suggesting custom builds. Handles setup, configuration, and security review for community connectors.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Rules for writing error messages, toasts, banners, and recovery copy in Rebel's voice — dry, calm, helpful, and never apologetic. Use whenever you add or rewrite any user-facing error string.
Guides users through adding new tools or capabilities to an existing connector (MCP server). Handles eligibility, workspace setup, connector research, implementation via Software Engineer workflow, local testing, and PR submission with an extension-specific template.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
| name | gmail-mcp-work-with |
| description | Key gotchas and practical tips for using Gmail MCP, based on real usage experience |
| last_updated | "2025-01-07T00:00:00.000Z" |
| tools_required | ["gmail MCP"] |
| dependencies | [] |
| agent_type | main_agent |
Key tips and gotchas from real usage of Gmail MCP.
| Tool ID | Purpose |
|---|---|
search_workspace_emails | Search/list emails with query filters |
get_workspace_email_thread | Get full thread conversation by thread ID |
send_workspace_email | Send email or reply (use replyToMessageId for replies) |
list_workspace_drafts / get_workspace_draft | Browse and inspect existing drafts |
create_workspace_draft / update_workspace_draft | Create or edit drafts (with optional attachments) |
send_workspace_draft / delete_workspace_draft | Send or discard a draft |
download_workspace_attachment / upload_workspace_attachment / delete_workspace_attachment | Per-action attachment tools (replace the legacy manage_workspace_attachment) |
THE BIG ONE: Gmail MCP cannot download attachment files.
Workaround: Generate URLs for manual access:
https://mail.google.com/mail/u/0/#inbox/{message_id}
Use the message id from search results as {message_id}.
Example workflow:
- [ ] [Invoice from vendor](https://mail.google.com/mail/u/0/#inbox/18c5f3a2b4d6e789)
Format: Must use YYYY/MM/DD for after: and before:
✅ Good: after:2024/11/01 before:2024/11/30
❌ Bad: after:11/01/2024 or after:2024-11-01
Different Gmail MCP instances may connect to different Google Workspace accounts.
Tip: Make sure you're using the correct instance for the account you're searching (personal vs work vs client-specific).
Common operators that work well:
from:sender@domain.com - filter by senderhas:attachment - only emails with attachmentsafter:2024/01/01 - date filters (use YYYY/MM/DD format)subject:"exact phrase" - subject line searchkeyword OR otherkeyword - combine termsWatch out for:
When building checklists from multiple email searches, use parallel tool calls to search multiple queries simultaneously.
Generate all URLs in one pass:
for message in search_results:
url = f"https://mail.google.com/mail/u/0/#inbox/{message.id}"
checklist.append(f"- [ ] [{message.subject}]({url})")
The Gmail API does not auto-include previous messages in the body — you must compose the full body yourself.
get_workspace_email_thread to fetch the conversation, compose your reply followed by quoted previous messages, then send with send_workspace_email using replyToMessageId.send_workspace_email (no replyToMessageId).See email-quoting skill for formatting conventions: plain text > quoting, HTML <blockquote>, forward headers, and attribution lines.
If Gmail MCP fails: