Skip to main content
Glama

modify_thread

Change labels on Gmail threads by adding or removing specific label IDs to organize email conversations.

Instructions

Modify the labels applied to a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the thread to modify
addLabelIdsNoA list of label IDs to add to the thread
removeLabelIdsNoA list of label IDs to remove from the thread

Implementation Reference

  • src/index.ts:775-789 (registration)
    Registration of the 'modify_thread' tool, including inline schema definition and handler function that modifies thread labels via Gmail API using threads.modify
    server.tool("modify_thread",
      "Modify the labels applied to a thread",
      {
        id: z.string().describe("The ID of the thread to modify"),
        addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the thread"),
        removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the thread")
      },
      async (params) => {
        const { id, ...threadData } = params
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.threads.modify({ userId: 'me', id, requestBody: threadData })
          return formatResponse(data)
        })
      }
    )
  • Handler executes tool logic: destructures thread ID, calls handleTool to invoke Gmail users.threads.modify with add/remove label IDs, formats response
    async (params) => {
      const { id, ...threadData } = params
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.threads.modify({ userId: 'me', id, requestBody: threadData })
        return formatResponse(data)
      })
    }
  • Zod schema for input parameters: required thread ID, optional arrays of label IDs to add/remove
    {
      id: z.string().describe("The ID of the thread to modify"),
      addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the thread"),
      removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the thread")
    },
  • Shared helper function handleTool that sets up OAuth2/Gmail client and executes the API call provided
    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}`
      }
    }
  • Helper to format API responses as MCP content blocks with JSON stringified data
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('modify') but doesn't specify permissions required, whether changes are reversible, error handling, or rate limits. This leaves significant gaps for an agent to understand the tool's behavior beyond basic functionality.

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 directly states the tool's function without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 moderate complexity (mutation with 3 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, and output, leaving room for improvement in completeness.

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, clearly documenting all three parameters (id, addLabelIds, removeLabelIds). The description adds no additional semantic context beyond what's in the schema, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 ('modify') and resource ('labels applied to a thread'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'update_label' or 'modify_message', which could involve similar label operations, so it doesn't reach the highest score.

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 'update_label' or 'patch_label', nor does it mention prerequisites or exclusions. It merely states what the tool does without contextual usage advice.

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