[BUG] Gmail MCP `create_draft` lost `threadId` parameter — drafts no longer thread into existing conversations

Preflight Checklist

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

What's Wrong?

The create_draft tool in the Gmail MCP plugin (claude-plugins-official, UUID: f567704a-3fa5-4b45-8d2c-ff6c7fe80710) no longer has a threadId parameter. As a result, all drafts are created as new standalone threads instead of replies within the original Gmail conversation.

What Should Happen?

create_draft should accept a threadId parameter so that the created draft is attached to an existing Gmail thread (Gmail API v1 supports this natively). Previously, this parameter existed and worked correctly.

Error Messages/Logs

No error is thrown. The draft is silently created as a new thread. Confirmed via `list_drafts`: the returned threadId is always a new ID, never the original thread's ID.

Steps to Reproduce

1. Install the Gmail MCP plugin from claude-plugins-official marketplace
2. Find an existing Gmail thread ID using search_threads
3. Call create_draft — observe that threadId is not available as a parameter
4. The created draft starts a new thread instead of replying to the original conversation

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude of windows 1.3109.0(35cbf6)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_