Skip to main content
Glama

get_message

Retrieve specific Gmail messages by ID with customizable format options for viewing email content and attachments.

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

  • Inline handler function for the 'get_message' MCP tool. It invokes the shared handleTool utility with an API callback that fetches the full Gmail message by ID, processes its payload (decoding bodies, filtering headers), and returns a formatted text/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)
      })
  • Input schema for 'get_message' tool using Zod: requires 'id' string (message ID), optional 'includeBodyHtml' boolean to control HTML body inclusion in response.
    {
      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")
    },
  • src/index.ts:542-559 (registration)
    Registration of the 'get_message' tool on the McpServer instance, specifying name, description, input schema, and 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)
        })
      }
    )
  • Core helper function used by 'get_message' (and all tools): handles OAuth2 client creation/validation, Gmail client setup, executes the provided Gmail API callback, catches errors.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Recursive helper to process Gmail message parts for 'get_message': decodes base64 bodies for text/* (html if flagged), recurses into parts, retains only key headers (Date, From, To, Subject, etc.).
    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
    }
Behavior2/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 of behavioral disclosure. It mentions 'format options' (referring to 'includeBodyHtml'), but doesn't describe other key behaviors: whether this is a read-only operation, potential error conditions (e.g., invalid ID), response format, or performance implications (e.g., size of returned data). For a retrieval 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, efficient sentence with zero waste. It front-loads the core purpose ('Get a specific message by ID') and adds a concise qualifier ('with format options'). Every word earns its place, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete for this tool's complexity. It's a retrieval tool with parameters, but lacks details on behavioral traits (e.g., read-only nature, error handling), output structure, or sibling differentiation. While concise, it doesn't compensate for the missing structured data, leaving the AI agent under-informed.

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 both parameters ('id' and 'includeBodyHtml'). The description adds minimal value beyond the schema by hinting at 'format options,' which loosely relates to 'includeBodyHtml.' However, it doesn't provide additional context like why HTML might be 'excessively large' (already in schema) or usage examples. Baseline 3 is appropriate given high schema coverage.

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'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_draft' or 'get_thread,' which also retrieve specific items by ID, leaving some ambiguity in sibling differentiation.

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 sibling tools like 'list_messages' for browsing or 'get_thread' for thread-level retrieval, nor does it specify prerequisites (e.g., needing a valid message ID). Usage is implied by the name and description but not explicitly stated, leaving gaps for an AI agent.

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/HitmanLy007/gmail-mcp'

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