Skip to main content
Glama

modify_message

Add or remove labels from a specific Gmail message using its ID. Streamline email organization by updating label assignments directly through Gmail MCP.

Instructions

Modify the labels on a message

Input Schema

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

Implementation Reference

  • src/index.ts:625-638 (registration)
    Registration of the 'modify_message' tool, including description, input schema, and inline handler function.
    server.tool("modify_message",
      "Modify the labels on a message",
      {
        id: z.string().describe("The ID of the message to modify"),
        addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the message"),
        removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the message")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.messages.modify({ userId: 'me', id: params.id, requestBody: { addLabelIds: params.addLabelIds, removeLabelIds: params.removeLabelIds } })
          return formatResponse(data)
        })
      }
    )
  • Handler function that executes the tool logic: calls handleTool wrapper which authenticates and invokes Gmail API users.messages.modify to update labels on a specific message.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.messages.modify({ userId: 'me', id: params.id, requestBody: { addLabelIds: params.addLabelIds, removeLabelIds: params.removeLabelIds } })
        return formatResponse(data)
      })
    }
  • Zod schema defining input parameters for the modify_message tool: message ID (required), optional label IDs to add or remove.
      id: z.string().describe("The ID of the message to modify"),
      addLabelIds: z.array(z.string()).optional().describe("A list of label IDs to add to the message"),
      removeLabelIds: z.array(z.string()).optional().describe("A list of label IDs to remove from the message")
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'modify' which implies mutation but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens if label IDs are invalid. The description adds minimal context beyond the basic action.

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 with zero waste. It's front-loaded with the core purpose and appropriately sized for the tool's complexity.

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 no annotations, no output schema, and a mutation tool with 3 parameters, the description is adequate but has clear gaps. It states what the tool does but lacks behavioral context, error handling, or output details. For a label modification tool, more guidance on label management would improve 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?

Schema description coverage is 100%, so the schema already documents all three parameters (id, addLabelIds, removeLabelIds) with clear descriptions. The description doesn't add meaning beyond what the schema provides, such as explaining label ID formats or interaction between add/remove operations. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Modify the labels on a message' clearly states the action (modify) and resource (labels on a message). It distinguishes from siblings like 'update_label' (which modifies label properties) or 'delete_label' (which removes labels entirely), but doesn't explicitly differentiate from 'batch_modify_messages' (which handles multiple messages).

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?

No guidance on when to use this tool versus alternatives like 'batch_modify_messages' for multiple messages or 'update_label' for label properties. The description implies usage for label modification on a single message but doesn't specify prerequisites, constraints, or exclusions.

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