Skip to main content
Glama
gmail-mcp
by gchallen

update_thread_labels

Add or remove labels on an entire Gmail thread in one call, letting you organize conversations by applying or clearing multiple label IDs at once.

Instructions

Add and remove labels on a whole thread in one call.

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": {
      "threadId": "<threadId>"
    },
    "name": "update_thread_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes
addLabelIdsNo
removeLabelIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds useful scope information by stating that changes apply to the whole thread rather than a single message. It says nothing about partial failures, unknown label IDs, or whether empty arrays are meaningful, which are the remaining behavioral unknowns.

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 tight sentence with no filler, front-loading the operation and its scope. Nothing is wasted or buried.

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 simple three-parameter tool with annotations and no output schema, the description covers the core operation adequately. It falls short on the mechanics an agent needs to call it safely: label ID format, empty-array behavior, and whether removals are additive or replace existing labels.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description must carry the semantics and largely does not. It implies the add/remove pairing but never mentions threadId, the expected ID format, or what happens when addLabelIds and removeLabelIds overlap.

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 names specific verbs and resource (add and remove labels) and scopes them to a whole thread, with 'in one call' signaling a batch operation. This distinguishes it from single-target siblings like label_thread and unlabel_thread, though those siblings are never named.

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?

Usage is only implied: 'a whole thread in one call' suggests it is the efficient choice when applying or clearing multiple labels across an entire thread. There is no explicit when-not guidance, no mention of prerequisites such as label IDs needing to exist, and no named alternative for single-message cases.

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