Skip to main content
Glama

get_message

Retrieve a specific Gmail message by its unique ID, with options to include or exclude parsed HTML content in the response, optimizing for data size and relevance.

Instructions

Get a specific message by ID with format options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the message to retrieve
includeBodyHtmlNoWhether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large

Implementation Reference

  • src/index.ts:575-591 (registration)
    Registration of the 'get_message' MCP tool using McpServer.tool(), including description, input schema validation with Zod, and the handler function.
    server.tool("get_message",
      "Get a specific message by ID with format options",
      {
        id: z.string().describe("The ID of the message to retrieve"),
        includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.messages.get({ userId: 'me', id: params.id, format: 'full' })
    
          if (data.payload) {
            data.payload = processMessagePart(data.payload, params.includeBodyHtml)
          }
    
          return formatResponse(data)
        })
      }
  • Handler function for the get_message tool. Fetches the Gmail message by ID using the Gmail API with full format, processes the payload (decodes body, handles parts, filters headers), and returns formatted JSON response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.messages.get({ userId: 'me', id: params.id, format: 'full' })
    
        if (data.payload) {
          data.payload = processMessagePart(data.payload, params.includeBodyHtml)
        }
    
        return formatResponse(data)
      })
    }
  • Zod input schema for get_message tool: requires 'id' (message ID string), optional 'includeBodyHtml' boolean.
    {
      id: z.string().describe("The ID of the message to retrieve"),
      includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large")
    },
  • Recursive helper to process Gmail message parts: decodes base64 bodies (text/plain/html if allowed), recurses on parts, filters to essential headers.
    const processMessagePart = (messagePart: MessagePart, includeBodyHtml = false): MessagePart => {
      if ((messagePart.mimeType !== 'text/html' || includeBodyHtml) && messagePart.body) {
        messagePart.body = decodedBody(messagePart.body)
      }
    
      if (messagePart.parts) {
        messagePart.parts = messagePart.parts.map(part => processMessagePart(part, includeBodyHtml))
      }
    
      if (messagePart.headers) {
        messagePart.headers = messagePart.headers.filter(header => RESPONSE_HEADERS_LIST.includes(header.name || ''))
      }
    
      return messagePart
    }
  • Helper to decode base64url-encoded message body data to UTF-8 string, used in processMessagePart.
    const decodedBody = (body: MessagePartBody) => {
      if (!body?.data) return body
    
      const decodedData = Buffer.from(body.data, 'base64').toString('utf-8')
      const decodedBody: MessagePartBody = {
        data: decodedData,
        size: body.data.length,
        attachmentId: body.attachmentId
      }
      return decodedBody
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'format options' (referring to includeBodyHtml), but doesn't describe what the tool returns (e.g., message metadata, body content), error conditions (e.g., invalid ID), permissions required, or rate limits. For a read operation with zero annotation coverage, this leaves significant behavioral gaps.

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 that front-loads the core purpose ('Get a specific message by ID') and adds a useful qualifier ('with format options'). There's no wasted language, repetition, or unnecessary elaboration, making it appropriately concise for this tool type.

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 tool's moderate complexity (retrieval with optional formatting), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what data is returned, how errors are handled, or authentication needs. For a tool that fetches potentially sensitive message data, more contextual information would be helpful for an AI agent to use it correctly.

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 fully documents both parameters (id and includeBodyHtml). The description adds minimal value beyond the schema, only implying that 'format options' relate to includeBodyHtml. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't provide additional parameter context like examples or edge cases.

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 tool's purpose: 'Get a specific message by ID with format options'. It specifies the verb ('Get'), resource ('message'), and key constraint ('by ID'), distinguishing it from sibling tools like 'list_messages' or 'get_thread'. However, it doesn't explicitly differentiate from other retrieval tools like 'get_draft' or 'get_thread', which slightly reduces clarity.

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 when to choose 'get_message' over 'list_messages' for retrieving multiple messages, or over 'get_thread' for thread context. There are no prerequisites, exclusions, or explicit alternatives stated, leaving usage context entirely implicit.

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

Related 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/shinzo-labs/gmail-mcp'

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