Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Get Gmail Message Content

get_gmail_message_content

Read-onlyIdempotent

Retrieve complete Gmail message details (subject, sender, recipients, body) with a full mode for untruncated content, including raw MIME export.

Instructions

Retrieves the full content (subject, sender, recipients, body) of a specific Gmail message.

Bodies are returned inline and truncated at 20,000 characters. Set full=True to get the complete, untruncated message instead: it is exported to disk and the response carries a short-lived download URL (HTTP transport) or file path (stdio transport) rather than the body, so large messages never stream through the model context. Stateless deployments have no file storage, so there full=True returns the untruncated body inline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`full`	No	When True, return the COMPLETE untruncated message: saved to local storage and referenced by download URL/file path instead of the body text, or inlined in the response when the server has no file storage (stateless mode). Use for messages large enough to hit the truncation limit, or when byte-exact fidelity is needed (pair with body_format='raw' for a .eml export).
`format`	No	Message format. "full" (default) includes the body and attachments, "metadata" only headers.	full
`message_id`	Yes	The unique ID of the Gmail message to retrieve.
`body_format`	No	Body output format (only applies when format='full'). 'text' (default) returns plaintext (HTML converted to text as fallback). 'html' returns the raw HTML body as-is without conversion. 'raw' fetches the full raw MIME message and returns the base64url-decoded content.	text
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.28.0Sep 24, 2026

changedInput schema / properties / body_format / description

Previous value: -"Body output format. 'text' (default) returns plaintext (HTML converted to text as fallback). 'html' returns the raw HTML body as-is without conversion. 'raw' fetches the full raw MIME message and returns the base64url-decoded content."New value: +"Body output format (only applies when format='full'). 'text' (default) returns plaintext (HTML converted to text as fallback). 'html' returns the raw HTML body as-is without conversion. 'raw' fetches the full raw MIME message and returns the base64url-decoded content."

addedInput schema / properties / format

Added value: +{
+  "default": "full",
+  "description": "Message format. \"full\" (default) includes\nthe body and attachments, \"metadata\" only headers.",
+  "enum": [
+    "full",
+    "metadata"
+  ],
+  "type": "string"
+}

Changed11 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / body_format

Added value: +{
+  "default": "text",
+  "description": "Body output format. 'text' (default) returns plaintext (HTML converted to text as fallback). 'html' returns the raw HTML body as-is without conversion. 'raw' fetches the full raw MIME message and returns the base64url-decoded content.",
+  "enum": [
+    "text",
+    "html",
+    "raw"
+  ],
+  "type": "string"
+}

addedInput schema / properties / full

Added value: +{
+  "default": false,
+  "description": "When True, return the COMPLETE untruncated message: saved to local storage and referenced by download URL/file path instead of the body text, or inlined in the response when the server has no file storage (stateless mode). Use for messages large enough to hit the truncation limit, or when byte-exact fidelity is needed (pair with body_format='raw' for a .eml export).",
+  "type": "boolean"
+}

addedInput schema / properties / message_id / description

Added value: +"The unique ID of the Gmail message to retrieve."

removedInput schema / properties / message_id / title
```
Removed value: -"Message Id"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "message_id",
-  "user_google_email"
-]New value: +[
+  "message_id",
+  "user_google_email"
+]

removedInput schema / title

Removed value: -"get_gmail_message_contentArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial behavioral detail beyond these: it discloses the 20,000-character inline truncation, the export-to-disk behavior for full=True, the transport-specific response (download URL for HTTP, file path for stdio), and the stateless fallback that inlines the untruncated body. This goes well beyond the annotations and paints a complete picture of side effects and response characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and a short paragraph, with no filler. It front-loads the core purpose, then explains the truncation and full=True behavior in a structured, efficient way. Every sentence contributes critical information about when and how to use the tool, and the structure guides the reader from basic behavior to edge cases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, idempotent tool with a full output schema, the description covers the essential behavioral nuances: truncation, full=True transport, and stateless handling. It does not detail error conditions or how to obtain message_id, but these are typically handled elsewhere. Given the output schema and annotations, the description is sufficient for an agent to call the tool correctly and interpret the response, with only minor omissions around edge-case error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so a baseline of 3 applies. The description adds value by explaining the implications of the full parameter: it clarifies the transport-specific behavior and stateless mode, which are not in the schema. It also ties full=True to body_format='raw' for .eml export. This adds meaningful context beyond the schema's own parameter descriptions, justifying a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise statement of the operation: 'Retrieves the full content (subject, sender, recipients, body) of a specific Gmail message.' This clearly identifies the resource (a specific Gmail message) and the verb (retrieves). It distinguishes the tool from batch and thread siblings by the singular scope, and from attachment tools by listing body content explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to prefer this tool over its siblings (e.g., get_gmail_messages_content_batch for multiple messages, get_gmail_thread_content for threads). However, it provides guidance on the full=True parameter, explaining when it should be used (large messages, byte-exact fidelity). The absence of alternative routing means an agent must infer single-message usage from the tool name and schema, making the guidance implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server