Skip to main content
Glama

list_threads

List threads from your Gmail mailbox using filters like query, labels, and pagination.

Instructions

List threads in the user's mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of threads to return
pageTokenNoPage token to retrieve a specific page of results
qNoOnly return threads matching the specified query
labelIdsNoOnly return threads with labels that match all of the specified label IDs
includeSpamTrashNoInclude threads 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:753-787 (registration)
    The 'list_threads' tool is registered on the MCP server via server.tool() with the name 'list_threads', a description, Zod schema for parameters, and an async 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)
        })
      }
    )
  • The handler function for 'list_threads' calls handleTool with a callback that invokes gmail.users.threads.list() with the provided parameters, then maps over the results to process message parts (optionally including HTML body) and returns the formatted 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)
        })
      }
    )
  • The Zod input schema for list_threads defines optional parameters: maxResults (number), pageToken (string), q (string query), labelIds (array of strings), includeSpamTrash (boolean), and includeBodyHtml (boolean).
    {
      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"),
    },
  • The handleTool helper function wraps the Gmail API call with OAuth2 credential validation and error handling, used by the list_threads handler.
    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}` });
      }
    }
Behavior2/5

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

No annotations are provided, and the description only says 'List threads' without disclosing behavior like ordering, authentication requirements, or whether it is read-only. It fails to add behavioral context beyond the minimal purpose.

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 concise sentence that is front-loaded and contains no unnecessary words. It efficiently states the tool's purpose.

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 description is minimal given the tool has 6 parameters, no output schema, and no annotations. It does not explain return values, ordering, defaults, or how threads are defined, leaving the agent with incomplete 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?

Input schema has 100% description coverage, so the schema already documents all parameters adequately. The description does not add any additional meaning beyond what is already in the schema, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool lists threads in the user's mailbox, using a specific verb and resource. It distinguishes from sibling tools like get_thread (single thread) and list_messages (messages, not threads).

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 such as get_thread or list_messages. It does not mention any context for selection among many thread-related siblings.

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

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