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

  • src/index.ts:580-608 (registration)
    Full registration of the 'list_messages' MCP tool, including description, input schema (Zod), and inline async handler function that invokes Gmail API.
    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)
        })
      }
  • Handler function executes Gmail users.messages.list API call with user params, processes each message payload (decodes body if applicable, filters headers), and formats the response as JSON text content.
    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)
      })
    }
  • Input schema using Zod for validating parameters like maxResults, q (search query), labelIds, etc., passed to Gmail API.
    {
      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"),
    },
  • Recursive helper to process message parts: decodes base64 bodies (except HTML unless flagged), recurses on parts, filters headers to response-relevant ones.
    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 wrapper for all tools: creates/validates OAuth2 client, builds Gmail client, executes provided API callback, handles 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}`
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List messages' implies a read-only operation, it doesn't specify authentication requirements, rate limits, pagination behavior (beyond the pageToken parameter), or what format the returned messages will have. This leaves significant gaps for an agent trying to understand how this tool behaves.

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 communicates the core functionality without unnecessary words. It's appropriately sized for a listing tool and gets straight to the point with no wasted verbiage.

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?

For a read-only listing tool with comprehensive parameter documentation (100% schema coverage), the description is minimally adequate. However, without annotations or an output schema, it should ideally provide more context about authentication needs, rate limits, or typical use cases to help an agent understand the complete operational context.

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?

The description mentions 'optional filtering' which aligns with parameters like q and labelIds, but doesn't add meaningful semantic context beyond what's already in the schema descriptions. With 100% schema description coverage, the baseline is 3, and the description doesn't significantly enhance understanding of parameter purposes or relationships.

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 resource ('in the user's mailbox'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other listing tools like list_drafts or list_threads, which would require mentioning it specifically lists email messages rather than other mailbox items.

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 mentions 'optional filtering' but provides no guidance on when to use this tool versus alternatives like list_threads or get_message. There's no mention of prerequisites, typical use cases, or comparison with sibling tools that might serve similar purposes.

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