Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Get Gmail Messages Content Batch

get_gmail_messages_content_batch
Read-onlyIdempotent

Retrieve content from up to 25 Gmail messages in a single batch by supplying message IDs and user email. Choose full or metadata format, with plain text, HTML, or raw MIME body output.

Instructions

Retrieves the content of multiple Gmail messages in a single batch request. Supports up to 25 messages per batch to prevent SSL connection exhaustion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoMessage format. "full" includes body, "metadata" only headers.full
body_formatNoBody 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
message_idsYesList of Gmail message IDs to retrieve (max 25 per batch).
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body_format
      Added value: +{
+  "default": "text",
+  "description": "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.",
+  "enum": [
+    "text",
+    "html",
+    "raw"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / format / description
      Added value: +"Message format. \"full\" includes body, \"metadata\" only headers."
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • addedInput schema / properties / message_ids / description
      Added value: +"List of Gmail message IDs to retrieve (max 25 per batch)."
    • removedInput schema / properties / message_ids / title
      Removed value: -"Message Ids"
    • 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_ids",
-  "user_google_email"
-]New value: +[
+  "message_ids",
+  "user_google_email"
+]
    • removedInput schema / title
      Removed value: -"get_gmail_messages_content_batchArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the 25-message limit and the rationale ('to prevent SSL connection exhaustion'), which is behavioral context beyond the annotations and schema.

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?

Two sentences, front-loaded with the core purpose, and every word earns its place. The second sentence explains a practical constraint without verbosity.

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?

The tool is straightforward, with full schema coverage and an output schema available. The description covers batch size and rationale, and the sibling list includes the singular variant, making the context clear. It doesn't discuss error handling or partial failures, but that's not critical for a read-only batch retriever.

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

Parameters3/5

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

Schema description coverage is 100%, with clear descriptions for all four parameters. The description does not add any parameter-specific detail beyond what the schema provides, so the baseline of 3 applies.

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 clearly states the tool retrieves content of multiple Gmail messages in a single batch request. The verb 'retrieves' with the resource 'Gmail messages' and the scope 'batch' distinctly differentiate it from the singular get_gmail_message_content sibling.

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

Usage Guidelines4/5

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

It provides the key context of batching up to 25 messages per request, which guides when to use this tool over the singular version. However, it does not explicitly say 'use this for multiple messages instead of single fetch' or name the alternative, so it falls short of explicit exclusion guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server