Skip to main content
Glama

get_message

Retrieve a specific Gmail message by its ID with options to include or exclude HTML content for efficient email access and management.

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

  • Handler for 'get_message' tool: retrieves a specific Gmail message by ID using the Gmail API with full format, processes the payload to decode bodies and filter headers, and returns formatted 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: requires message ID, optional flag to include HTML bodies.
    {
      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:561-578 (registration)
    Registration of the 'get_message' MCP tool on the server, including name, description, schema, and handler.
    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)
        })
      }
    )
  • Helper function processMessagePart used in get_message handler to recursively decode message bodies (unless HTML excluded) and filter headers to a predefined list.
    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
    }
  • Shared helper handleTool wraps API calls with OAuth2 authentication, credential validation, and Gmail client creation for all tools including get_message.
    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}`
      }
    }
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' (via includeBodyHtml), but doesn't describe other key behaviors: whether it's read-only (implied by 'Get'), error handling for invalid IDs, rate limits, authentication needs, or return format. For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how it operates.

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 detail ('with format options'). There's no wasted verbiage, repetition, or unnecessary elaboration—every word earns its place.

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?

Given the tool's low complexity (retrieval with 2 parameters) and high schema coverage (100%), the description is adequate but incomplete. It lacks output details (no output schema provided), behavioral context (no annotations), and usage guidance. For a simple getter, it's minimally viable but leaves the agent to guess about return values and operational constraints.

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 by hinting at 'format options', which loosely relates to includeBodyHtml, but doesn't provide additional syntax or context. This meets the baseline of 3 when the schema does the heavy lifting.

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'), which distinguishes it from sibling tools like 'list_messages' or 'get_thread'. However, it doesn't explicitly differentiate from 'get_draft' or 'get_thread', which also retrieve specific items by ID, so it's not fully sibling-distinctive.

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). The agent must infer usage from the name and parameters alone.

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

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