[BUG] gmail_read_message has now been removed

Resolved 💬 15 comments Opened Apr 15, 2026 by cheekyjeremy Closed Jun 22, 2026

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?

It appears that the gmail map has now removed the gmail_read_message tool. At this point, there is no way to get data from an email for use. The get_thread tool does not retrieve much more than snippets and has broken basically all of my skills. I wanted to check if this is an issue for others

What Should Happen?

Claude should be able to read email, parse data to launch skills in next steps. Continually fails to get data stating that the gmail_read_message is no longer listed as a tool

Error Messages/Logs

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.

Steps to Reproduce

Simply ask Claude if they can access the gmail_read_message tool

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 1.2581.0 (f10398) 2026-04-14T17:16:40.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 15 comments on GitHub. Read the full discussion on GitHub ↗