Skip to main content
Glama

batch_modify_messages

Modify labels on multiple Gmail messages simultaneously to organize your inbox efficiently. Add or remove labels from selected messages in bulk.

Instructions

Modify the labels on multiple messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesThe IDs of the messages to modify
addLabelIdsNoA list of label IDs to add to the messages
removeLabelIdsNoA list of label IDs to remove from the messages

Implementation Reference

  • Handler function for the 'batch_modify_messages' tool. It uses handleTool to execute the Gmail API call to batchModify messages with specified label additions/removals.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.messages.batchModify({ userId: 'me', requestBody: { ids: params.ids, addLabelIds: params.addLabelIds, removeLabelIds: params.removeLabelIds } })
        return formatResponse(data)
      })
    }
  • Zod schema defining input parameters for the batch_modify_messages tool: ids (required array of strings), addLabelIds and removeLabelIds (optional arrays).
      ids: z.array(z.string()).describe("The IDs of the messages to modify"),
      addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the messages"),
      removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the messages")
    },
  • src/index.ts:533-546 (registration)
    Registration of the 'batch_modify_messages' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool("batch_modify_messages",
      "Modify the labels on multiple messages",
      {
        ids: z.array(z.string()).describe("The IDs of the messages to modify"),
        addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the messages"),
        removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the messages")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.messages.batchModify({ userId: 'me', requestBody: { ids: params.ids, addLabelIds: params.addLabelIds, removeLabelIds: params.removeLabelIds } })
          return formatResponse(data)
        })
      }
    )
  • Shared helper function used by batch_modify_messages (and other tools) to handle OAuth2 authentication, client creation, and execution of Gmail API calls.
    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 'modify' implies mutation, it doesn't specify permission requirements, whether changes are reversible, rate limits, or what happens if label IDs don't exist. For a batch mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 gets straight to the point with zero wasted words. It's appropriately sized for the tool's complexity and front-loads the essential information about modifying labels on multiple messages.

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?

For a batch mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like error handling, response format, atomicity of batch operations, or how it differs from single-message modification. The 100% schema coverage helps, but doesn't compensate for missing behavioral and output information.

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?

Schema description coverage is 100%, so the schema already fully documents all three parameters (ids, addLabelIds, removeLabelIds). The description adds no additional parameter semantics beyond what's in the schema, such as format examples, constraints, or relationships between parameters. The baseline score of 3 reflects adequate but minimal value addition.

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 on multiple messages'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'modify_message' by specifying batch operations, though it doesn't explicitly contrast with other label-related tools like 'create_label' or 'update_label'.

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. It doesn't mention when to prefer batch_modify_messages over modify_message for single messages, or how it relates to label management tools like create_label or update_label. There are no usage prerequisites or exclusions stated.

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