Skip to main content
Glama
gmail-mcp
by gchallen

label_thread

Adds one or more labels to every message in a Gmail thread and applies user labels to future messages in that thread.

Instructions

Add labels to every message in a thread (and, for user labels, future messages in it).

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>",
      "labelIds": "<labelIds>"
    },
    "name": "label_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdsYes
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive mutation (readOnlyHint=false, destructiveHint=false), so the bar is lower. The description nonetheless adds a genuinely non-obvious behavioral trait: labels propagate to future messages in the thread when they are user labels, which the agent cannot learn from annotations or schema.

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 primary scope first and the conditional nuance in a parenthetical. No filler, nothing to trim.

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?

With no output schema and 0% schema description coverage, the description carries more burden than it does. It covers the core effect and the future-message nuance, but omits parameter documentation and any sense of the result or failure modes for a two-required-parameter mutation.

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 0%, so the schema offers no parameter documentation; the description partially compensates by distinguishing user labels (which propagate) from other labels, implying labelIds is a list of label identifiers. It says nothing about threadId's format or what happens with invalid or duplicate label IDs.

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?

States a specific verb and resource: 'Add labels to every message in a thread.' The scope word 'every message in a thread' implicitly separates it from message-level siblings like label_message or update_thread_labels, though no sibling is named explicitly.

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?

There is no explicit when-to-use guidance, no prerequisites, and no exclusion of alternatives. An agent must infer from the scope phrase alone that this is a thread-wide label operation rather than a single-message label or a label replacement (update_thread_labels).

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