Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Gmail create_draft tool missing threadId parameter (regression from gmail_create_draft) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48681•Fetched 2026-04-16 06:53:52
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
melissa970melissa970
Participants
github-actions[bot]github-actions[bot]melissa970melissa970
Timeline (top)
labeled ×4commented ×1

Error Message

Error: There's no runtime error message — the issue is a missing parameter. When Claude inspects the create_draft schema via ToolSearch, threadId simply isn't there. Any attempt to pass it fails with InputValidationError because the schema doesn't accept it.

Root Cause

Error: There's no runtime error message — the issue is a missing parameter. When Claude inspects the create_draft schema via ToolSearch, threadId simply isn't there. Any attempt to pass it fails with InputValidationError because the schema doesn't accept it.

Code Example

Error: There's no runtime error message — the issue is a missing parameter. When Claude inspects the create_draft schema via ToolSearch, threadId simply isn't there. Any attempt to pass it fails with InputValidationError because the schema doesn't accept it.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Description The create_draft tool in the Google Workspace Gmail integration is missing the threadId parameter that existed in the previous gmail_create_draft tool. This means drafts can no longer be created as in-thread replies — they all save as standalone new emails instead.

Previous behavior The old gmail_create_draft tool accepted a threadId parameter. Passing a thread's ID caused the draft to be saved as a reply within that thread in Gmail.

Current behavior The new create_draft tool has no threadId parameter. All drafts save as standalone emails with no thread association, regardless of subject line.

Steps to reproduce

  1. Use the create_draft tool with a threadId field
  2. Tool returns an error ("Tool execution failed")
  3. Without threadId, draft saves as a new standalone email

Expected behavior create_draft should accept a threadId parameter so drafts can be placed in-thread as replies.

Environment

  • Claude Code with Google Workspace Gmail MCP integration
  • Integration ID: d0ba6c0b-1d1c-4a8f-9e42-16fcf4984618

What Should Happen?

create_draft should accept a threadId parameter so drafts can be placed in-thread as replies.

Error Messages/Logs

Error: There's no runtime error message — the issue is a missing parameter. When Claude inspects the create_draft schema via ToolSearch, threadId simply isn't there. Any attempt to pass it fails with InputValidationError because the schema doesn't accept it.

Steps to Reproduce

Steps to replicate:

Connect the Gmail MCP server (Google Workspace connector) in Claude Code Use ToolSearch to fetch the create_draft schema — confirm threadId is not listed as a parameter Attempt to draft a reply to an existing email thread — the draft will appear as a new standalone email in Gmail, not as a reply inside the thread Compare to the previous gmail_create_draft tool schema, which included threadId as a supported parameter Expected behavior: create_draft should accept a threadId parameter so drafts can be created as in-thread replies, matching the behavior of the previous tool.

Impact: Any workflow that drafts customer support replies (or any replies) using the Gmail MCP server produces standalone emails that are disconnected from the original thread — requiring manual copy-paste to fix before sending.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

claude code sonnet 4.6

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The create_draft tool in the Google Workspace Gmail integration is missing the threadId parameter, causing drafts to be saved as standalone emails instead of in-thread replies.

Guidance

  • Review the create_draft tool schema to confirm the absence of the threadId parameter.
  • Compare the current schema with the previous gmail_create_draft tool schema to identify the missing parameter.
  • Consider reaching out to the development team or support to request the addition of the threadId parameter to the create_draft tool.
  • As a temporary workaround, manually copy and paste the draft into the original email thread to maintain thread association.

Example

No code snippet is provided as the issue is related to a missing parameter in the create_draft tool schema.

Notes

The issue is confirmed to be a regression, as the previous gmail_create_draft tool included the threadId parameter. The exact version where this worked is not specified.

Recommendation

Apply workaround: Manually copy and paste the draft into the original email thread to maintain thread association, until the threadId parameter is added to the create_draft tool.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#runtime error#GPU compatibility#latency issue#model loading

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING