Gmail MCP: Draft link fails to open with no error feedback
Resolved 💬 2 comments Opened Apr 8, 2026 by Ariel-Meneses Closed Apr 11, 2026
Description
When using the gmail_create_draft MCP tool, occasionally the draft is created successfully (draftId is returned), but the provided draft link fails to open in the browser. The user receives no error message or feedback — it appears to succeed silently, but Gmail never opens.
Expected Behavior
One of the following:
- The draft link opens successfully in Gmail
- An error is returned if the link is invalid or authentication fails
- User receives explicit feedback that the action failed
Actual Behavior
gmail_create_draftreturnsdraftIdandmessage: "Draft created successfully"- User attempts to click the link or access the draft
- Browser does not open Gmail (no popup, no tab, nothing)
- No error message is shown to the user
- User assumes it worked, only to discover the draft is missing when checking Gmail
Impact
- User Experience: Silent failure — looks like success but isn't
- Debugging difficulty: No clear indication of what went wrong
- Workaround required: User must manually go to Gmail and find the draft (if it exists)
Reproduction
- Uncertain (occurred at least once in production)
- Possible causes:
- Popup blocker in browser
- Authentication token expired or invalid
- Generated URL is malformed
- Session timeout
Workaround
- Check Gmail drafts folder manually
- Ask tool to regenerate the draft link
Suggested Solutions
- Validate the draft URL before returning it to ensure it's correct
- Add error handling — if link generation fails, return explicit error instead of silent failure
- Return additional context — include draftId and/or direct Gmail URL so user can access manually if needed
- Add logging — log when draft creation succeeds but link fails to open (for debugging)
Environment
- OS: Windows 11 Pro
- Tool:
gmail_create_draftMCP - Context: Creating email drafts for business communication
---
Related: This is a continuation of production testing for Claude Code. User is actively reporting real-world issues to improve tool reliability.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗