Skip to main content
Glama
gmail-mcp
by gchallen

update_message_labels

Add or remove labels on a single Gmail message in one call, enabling moving between labels or marking messages read and archived together.

Instructions

Add and remove labels on one message in a single call, e.g. move between labels or mark read and archive 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": {
      "messageId": "<messageId>"
    },
    "name": "update_message_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes
addLabelIdsNo
removeLabelIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, open-world behavior. The description usefully adds that add and remove are combined into one atomic-looking call, but says nothing about permissions, what happens on unknown label IDs, or whether omitted fields are untouched.

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?

A single front-loaded sentence with the capability first and concrete examples second; no filler or restatement of the tool name.

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?

For a 3-parameter mutation with no output schema and no schema descriptions, the definition is minimally adequate: it conveys the add/remove duality but not parameter formats, failure behavior, or what the response contains.

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 description names the two operations (add/remove label ids) but not messageId semantics or the ID format, and with 0% schema coverage it leaves much undocumented. The "mark read and archive" example does hint that system labels (UNREAD, INBOX) are valid remove values, which adds real meaning beyond the bare schema.

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?

"Add and remove labels on one message in a single call" states a specific verb pair and resource, and "one message" implicitly distinguishes it from thread-level siblings like update_thread_labels. It stops short of naming an alternative, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples ("move between labels or mark read and archive at once") imply when to reach for this over single-purpose siblings such as label_message or unlabel_message, but there is no explicit when-to-use/when-not statement or named alternative.

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