Skip to main content
Glama

list_messages

Retrieve and filter email messages from your Gmail inbox using search queries, labels, and pagination controls to manage your mailbox efficiently.

Instructions

List messages in the user's mailbox with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of messages to return. Accepts values between 1-500
pageTokenNoPage token to retrieve a specific page of results
qNoOnly return messages matching the specified query. Supports the same query format as the Gmail search box
labelIdsNoOnly return messages with labels that match all of the specified label IDs
includeSpamTrashNoInclude messages from SPAM and TRASH in the results
includeBodyHtmlNoWhether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large

Implementation Reference

  • The handler function for the 'list_messages' tool. It invokes the Gmail API's users.messages.list method with user-provided parameters, processes each message's payload by decoding bodies and filtering headers if applicable, and returns a formatted JSON response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.messages.list({ userId: 'me', ...params })
    
        if (data.messages) {
          data.messages = data.messages.map((message: Message) => {
            if (message.payload) {
              message.payload = processMessagePart(
                message.payload,
                params.includeBodyHtml
              )
            }
            return message
          })
        }
    
        return formatResponse(data)
      })
    }
  • The Zod input schema for the 'list_messages' tool, defining optional parameters for pagination, querying, filtering by labels, including spam/trash, and body processing options.
    {
      maxResults: z.number().optional().describe("Maximum number of messages to return. Accepts values between 1-500"),
      pageToken: z.string().optional().describe("Page token to retrieve a specific page of results"),
      q: z.string().optional().describe("Only return messages matching the specified query. Supports the same query format as the Gmail search box"),
      labelIds: z.array(z.string()).optional().describe("Only return messages with labels that match all of the specified label IDs"),
      includeSpamTrash: z.boolean().optional().describe("Include messages from SPAM and TRASH in the results"),
      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-590 (registration)
    The registration of the 'list_messages' tool on the MCP server using server.tool(), specifying name, description, schema, and handler.
    server.tool("list_messages",
      "List messages in the user's mailbox with optional filtering",
      {
        maxResults: z.number().optional().describe("Maximum number of messages to return. Accepts values between 1-500"),
        pageToken: z.string().optional().describe("Page token to retrieve a specific page of results"),
        q: z.string().optional().describe("Only return messages matching the specified query. Supports the same query format as the Gmail search box"),
        labelIds: z.array(z.string()).optional().describe("Only return messages with labels that match all of the specified label IDs"),
        includeSpamTrash: z.boolean().optional().describe("Include messages from SPAM and TRASH in the results"),
        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.list({ userId: 'me', ...params })
    
          if (data.messages) {
            data.messages = data.messages.map((message: Message) => {
              if (message.payload) {
                message.payload = processMessagePart(
                  message.payload,
                  params.includeBodyHtml
                )
              }
              return message
            })
          }
    
          return formatResponse(data)
        })
      }
    )
  • Helper function used in the handler to recursively process message parts: decodes base64 data to UTF-8 for text bodies (plain and optionally HTML), recurses on multipart, and filters 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 function used by the handler (and other tools) to manage OAuth2 authentication, validate credentials, create Gmail client, execute the API call, and handle 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}`
      }
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only mentions 'optional filtering' without explaining key behaviors like pagination, rate limits, or return format. This is insufficient for an agent to understand what to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (one sentence) but lacks structure and detail. While concise, it could be improved with brief examples or hints about common use cases.

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?

The schema covers parameters well, but the description does not explain the return value (e.g., list of message summaries) or pagination behavior. For a tool with 6 parameters and no output schema, more context is needed for complete understanding.

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?

All parameters have complete descriptions in the input schema (100% coverage), so the description adds no additional meaning. Baseline score of 3 is appropriate.

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 (list messages) and scope (user's mailbox) with optional filtering. However, it does not differentiate from sibling tools like list_drafts or list_threads, which could cause ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_message for a single message, batch_delete for deletions). The description lacks any usage context.

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