claude-code - 💡(How to fix) Fix [BUG] gmail_read_message has now been removed [2 comments, 2 participants]

WHAT CHANGED:
The Gmail connector (UUID: 1ec2656e-2aa2-4ae2-beb6-b7abf9f7f0a9) previously exposed two tools called "gmail_read_message" and "gmail_search_messages." These tools have been replaced with "get_thread" and "search_threads." The new "get_thread" tool does not return message bodies or attachment content, even when called with messageFormat: "FULL_CONTENT." It only returns metadata (date, sender, subject, snippet, recipients).

WHAT THIS BROKE:
I have a flight confirmation processor skill that monitors a Gmail label for airline booking emails, extracts flight data from the email bodies and attachments, and updates a travel spreadsheet. This skill has been running successfully across dozens of sessions since late March 2026. As of today (April 15, 2026), it no longer works because the connector cannot read email content.

EVIDENCE:
- Multiple prior sessions (visible in session history) successfully used gmail_read_message on the same connector UUID to read full email bodies and attachments from airlines including United, Delta, Southwest, Alaska, and Sabre/GDS confirmations.
- The current session's get_thread tool returns identical truncated output regardless of whether FULL_CONTENT is specified or omitted.
- The connector shows as connected and enabled in settings. Reconnecting did not resolve the issue. Multiple fresh sessions exhibit the same behavior.

IMPACT:
This is a complete blocker for any workflow that depends on reading email content, which is arguably the core purpose of a Gmail connector.

REQUEST:
Please restore the ability to read full message bodies and attachments, whether through restoring gmail_read_message or fixing get_thread to actually return full content as its documentation claims.