Skip to main content
Glama

list_threads

Retrieve and organize email threads in your Gmail mailbox using filters, labels, and pagination. Supports querying, label-based filtering, and including spam/trash results for efficient thread management.

Instructions

List threads in the user's mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeBodyHtmlNoWhether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large
includeSpamTrashNoInclude threads from SPAM and TRASH in the results
labelIdsNoOnly return threads with labels that match all of the specified label IDs
maxResultsNoMaximum number of threads to return
pageTokenNoPage token to retrieve a specific page of results
qNoOnly return threads matching the specified query

Implementation Reference

  • Handler function for the 'list_threads' tool. It invokes handleTool to authenticate, calls the Gmail API to list threads with given parameters, processes thread messages by decoding payloads if includeBodyHtml is true, and formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.threads.list({ userId: 'me', ...params })
    
        if (data.threads) {
          data.threads = data.threads.map(thread => {
            if (thread.messages) {
              thread.messages = thread.messages.map(message => {
                if (message.payload) {
                  message.payload = processMessagePart(
                    message.payload,
                    params.includeBodyHtml
                  )
                }
                return message
              })
            }
            return thread
          })
        }
    
        return formatResponse(data)
      })
    }
  • Zod input schema defining parameters for the list_threads tool: maxResults, pageToken, q (query), labelIds, includeSpamTrash, includeBodyHtml.
      maxResults: z.number().optional().describe("Maximum number of threads to return"),
      pageToken: z.string().optional().describe("Page token to retrieve a specific page of results"),
      q: z.string().optional().describe("Only return threads matching the specified query"),
      labelIds: z.array(z.string()).optional().describe("Only return threads with labels that match all of the specified label IDs"),
      includeSpamTrash: z.boolean().optional().describe("Include threads 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:753-787 (registration)
    Registration of the 'list_threads' MCP tool on the server, including name, description, input schema, and handler function.
    server.tool("list_threads",
      "List threads in the user's mailbox",
      {
        maxResults: z.number().optional().describe("Maximum number of threads to return"),
        pageToken: z.string().optional().describe("Page token to retrieve a specific page of results"),
        q: z.string().optional().describe("Only return threads matching the specified query"),
        labelIds: z.array(z.string()).optional().describe("Only return threads with labels that match all of the specified label IDs"),
        includeSpamTrash: z.boolean().optional().describe("Include threads 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.threads.list({ userId: 'me', ...params })
    
          if (data.threads) {
            data.threads = data.threads.map(thread => {
              if (thread.messages) {
                thread.messages = thread.messages.map(message => {
                  if (message.payload) {
                    message.payload = processMessagePart(
                      message.payload,
                      params.includeBodyHtml
                    )
                  }
                  return message
                })
              }
              return thread
            })
          }
    
          return formatResponse(data)
        })
      }
    )
  • Shared helper function used by all Gmail tools, including list_threads, to handle OAuth2 authentication, 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) {
        // Check for specific authentication errors
        if (
          error.message?.includes("invalid_grant") ||
          error.message?.includes("refresh_token") ||
          error.message?.includes("invalid_client") ||
          error.message?.includes("unauthorized_client") ||
          error.code === 401 ||
          error.code === 403
        ) {
          return formatResponse({
            error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`,
          });
        }
    
        return formatResponse({ error: `Tool execution failed: ${error.message}` });
      }
    }
  • Helper function to recursively process and decode message parts (base64 to utf-8), filter headers, used in list_threads handler to prepare thread messages.
    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 must fully disclose behavioral traits. It states the tool lists threads but fails to mention critical behaviors such as pagination (implied by 'pageToken' in schema but not described), default sorting, rate limits, authentication requirements, or what constitutes a 'thread' versus a 'message'. This leaves significant gaps in understanding how the tool 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, clear sentence with no wasted words, making it highly concise and front-loaded. It directly states the tool's purpose without unnecessary elaboration, which is efficient for an AI agent.

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 complexity of listing threads in a mailbox with 6 parameters and no output schema, the description is insufficient. It does not explain the return format, pagination behavior, or how threads differ from messages, leaving the agent without key context needed to use the tool effectively. The lack of annotations exacerbates this gap.

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 input schema has 100% description coverage, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond the schema, as it does not explain parameters like 'labelIds' or 'q' in context. This meets the baseline score of 3, since the schema carries the burden of parameter documentation.

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') and resource ('threads in the user's mailbox'), making the purpose immediately understandable. However, it does not differentiate this tool from its sibling 'list_messages' or other listing tools, which would require specifying what distinguishes threads from messages or other listable entities.

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 like 'list_messages' or 'get_thread'. It lacks any context about use cases, prerequisites, or comparisons to sibling tools, leaving the agent to infer usage based on the tool name 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

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