fastmcp-gsuite

by tumf

Overview Schema Source Related Servers Discussions Admin

Python

Remote

bulk_get_gmail_emails

Retrieve multiple Gmail messages by their IDs in a single request, including bodies and attachment metadata.

Instructions

Retrieves multiple Gmail email messages by their IDs in a single request, including bodies and attachment metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>",
      "email_ids": "<email_ids>"
    },
    "name": "bulk_get_gmail_emails"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	The EMAIL of the Google account. Choose from:
`email_ids`	Yes	List of Gmail message IDs to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 21, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves bodies and attachment metadata, which is helpful, but does not address potential side effects (e.g., marking as read) or limitations (e.g., rate limits, maximum IDs).

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 a single, efficient sentence of 14 words that conveys the core functionality without any unnecessary elaboration.

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

Completeness3/5

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

For a bulk retrieval tool, the description is adequate but lacks details on output format, error handling, or limits. It mentions including bodies and attachment metadata but does not clarify how to access actual attachment files, which may require downstream tools like download_drive_file.

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 the schema already documents both parameters adequately. The description adds context about including bodies and attachment metadata, which gives insight into the output but does not significantly enhance parameter understanding beyond the schema.

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 multiple Gmail email messages by IDs, including bodies and attachment metadata, distinguishing it from siblings like get_email_details (single message) and query_gmail_emails (search).

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 implies use for bulk retrieval via 'by their IDs in a single request' but does not explicitly state when to use over alternatives like get_email_details for single messages or mention any prerequisites or limitations.

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