Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Gmail Threads Content Batch

get_gmail_threads_content_batch
Read-onlyIdempotent

Retrieve content from multiple Gmail threads in one batched request, automatically chunked in groups of 25 to avoid SSL connection exhaustion. Use it to pull thread bodies in text, HTML, or raw formats.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
thread_idsYesA list of Gmail thread IDs to retrieve. The function will automatically batch requests in chunks of 25.
body_formatNoBody output format. 'text' (default) returns plaintext (HTML converted to text as fallback). 'html' returns the raw HTML body as-is without conversion. 'raw' fetches each message's full raw MIME content and returns the base64url-decoded body.text
include_linksNoWhen True, append a LINKS section listing the http(s) URLs from the HTML body that the text output omits. Only applies to body_format='text'.
user_google_emailYesThe user's Google email address. Required.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / include_links
      Added value: +{
+  "default": false,
+  "description": "When True, append a LINKS section listing the http(s) URLs from the HTML body that the text output omits. Only applies to body_format='text'.",
+  "type": "boolean"
+}
  2. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. The description adds useful operational context by noting the 25-thread batch limit and the reason for it: avoiding SSL connection exhaustion. It does not describe return shape, but an output schema exists.

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 tight sentences with no wasted language. The batch purpose is front-loaded, followed immediately by the important operational limit.

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 description is sufficient for calling the tool correctly given rich annotations, 100% schema coverage, and an output schema. Its main gap is contextual routing: it does not explicitly distinguish this batch thread reader from single-thread or batch-message siblings.

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%, so parameters such as body_format, include_links, and user_google_email are already fully documented. The description only reinforces the thread_ids batching behavior and the 25-thread limit, so it adds some value but not much beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource: it retrieves content for multiple Gmail threads in one batch request. It clearly implies a batch-oriented variant of thread retrieval, though it does not explicitly name the single-thread sibling get_gmail_thread_content or other message-search alternatives.

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 batching language implies this tool is for retrieving multiple thread contents efficiently, and the 25-thread limit gives a practical usage boundary. However, it does not explicitly say when to choose this over get_gmail_thread_content, get_gmail_messages_content_batch, or search_gmail_messages, nor does it state exclusions.

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

Deploy Server

Other Tools