google-workspace-alias-mcp

batch_modify_emails

Add or remove labels on multiple Gmail messages using message IDs. Batch modify email labels to organize your inbox.

Instructions

Modify labels for multiple emails at once

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "messageIds": "<messageIds>"
    },
    "name": "batch_modify_emails"
  }
}

Input Schema

Name	Required	Description
`messageIds`	Yes	List of message IDs to modify
`addLabelIds`	No	Labels to add
`removeLabelIds`	No	Labels to remove

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must cover behavior. It only states the basic operation but does not disclose atomicity, failure handling, or limits on message IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, direct and to the point. Could be improved by including more context without becoming overly long.

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?

No output schema and no annotations. Description lacks details on return value, error handling, performance, or prerequisites. Minimal for a batch operation.

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 coverage is 100% with descriptions for all three parameters. The tool description adds no additional meaning beyond what the schema already provides.

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 the action (modify), the resource (labels for multiple emails), and implicitly distinguishes from siblings like modify_email (single email) and batch_delete_emails (delete).

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 explicit guidance on when to use this tool vs. alternatives (e.g., calling modify_email repeatedly). The sibling tool modify_email exists but no comparison is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.