Skip to main content
Glama
ricleedo

Google Services MCP Server

by ricleedo

gmail-get-email

Retrieve a specific Gmail email using its message ID to access individual messages within the Google Services MCP Server.

Instructions

Get a specific email by message ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesGmail message ID

Implementation Reference

  • The handler function that retrieves a specific Gmail email by message ID using the Google Gmail API, extracts headers and body (handling multipart), truncates long body, formats as Markdown using formatEmailToMarkdown, and returns structured content.
    export async function getEmail(params: z.infer<typeof getEmailSchema>) {
      try {
        const auth = createGmailAuth();
        const gmail = google.gmail({ version: "v1", auth });
    
        const response = await gmail.users.messages.get({
          userId: "me",
          id: params.messageId,
          format: "full",
        });
    
        const message = response.data;
        const headers = message.payload?.headers || [];
        const getHeader = (name: string) =>
          headers.find((h) => h.name?.toLowerCase() === name.toLowerCase())
            ?.value || "";
    
        // Extract body content
        let body = "";
        if (message.payload?.body?.data) {
          body = Buffer.from(message.payload.body.data, "base64").toString();
        } else if (message.payload?.parts) {
          // Handle multipart messages
          for (const part of message.payload.parts) {
            if (part.mimeType === "text/plain" && part.body?.data) {
              body = Buffer.from(part.body.data, "base64").toString();
              break;
            }
          }
        }
    
        // Truncate body if it exceeds 30000 characters
        const truncatedBody =
          body.length > 20000
            ? body.substring(0, 20000) +
              "\n\n[Email body truncated - content too long]"
            : body;
    
        const emailDetail = {
          id: message.id,
          threadId: message.threadId,
          from: getHeader("From"),
          to: getHeader("To"),
          cc: getHeader("Cc"),
          bcc: getHeader("Bcc"),
          subject: getHeader("Subject"),
          date: getHeader("Date"),
          body: truncatedBody,
          snippet: message.snippet,
          labelIds: message.labelIds,
        };
    
        return {
          content: [
            {
              type: "text" as const,
              text: formatEmailToMarkdown(emailDetail),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error getting email: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema for input validation: requires 'messageId' as a string.
    export const getEmailSchema = z.object({
      messageId: z.string().describe("Gmail message ID"),
    });
  • src/index.ts:200-207 (registration)
    MCP server registration of the 'gmail-get-email' tool, using getEmailSchema and delegating to the getEmail handler.
    server.tool(
      "gmail-get-email",
      "Get a specific email by message ID",
      getEmailSchema.shape,
      async (params) => {
        return await getEmail(params);
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose authentication needs, rate limits, error handling, or what data is returned (e.g., full email content vs. metadata). For a tool with zero annotation coverage, this is insufficient.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool, making it highly efficient.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'Get' returns (e.g., email body, headers, attachments) or behavioral aspects like permissions. For a tool interacting with a complex system like Gmail, more context is needed.

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 the single parameter 'messageId' well-documented in the schema. The description adds no additional parameter semantics beyond implying retrieval by ID, so it meets the baseline for high schema coverage without adding value.

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 clearly states the action ('Get') and resource ('a specific email by message ID'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'gmail-read-emails' or 'gmail-get-labels', which would be needed for a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid message ID), contrast with 'gmail-read-emails' for listing emails, or specify error conditions. This leaves the agent to infer usage context.

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/ricleedo/Google-Service-MCP'

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