Skip to main content
Glama
gmail-mcp
by gchallen

unlabel_thread

Remove labels from every message in a Gmail thread. Removing INBOX archives the conversation, while removing UNREAD marks it as read.

Instructions

Remove labels from every message in a thread. Removing INBOX archives the conversation; removing UNREAD marks it read.

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": "unlabel_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdsYes
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark this as mutating and non-read-only, but the description adds non-obvious side effects: INBOX removal archives the conversation and UNREAD removal marks it read. It still omits auth, idempotency, and behavior for other labels, so not a 5.

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?

Two sentences, front-loaded with the action and followed by the two special label effects. No redundant wording or repetition of schema details.

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 two-parameter mutation, the description covers purpose and key label-removal side effects. However, with no output schema and 0% parameter coverage, it leaves out return behavior, error/idempotency expectations, and permissions, making it adequate but incomplete.

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 description must carry meaning. It mentions the thread and the label IDs indirectly and adds valuable semantics for INBOX and UNREAD, but it does not explain threadId format, labelIds array shape, or allowed values beyond those two system labels.

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 first sentence gives a specific verb and scope: remove labels from every message in a thread. This distinguishes it from the message-level sibling unlabel_message and from label_thread by operation direction, even without naming alternatives.

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 by the action; it does not explicitly say when to choose this over unlabel_message, update_thread_labels, or label_thread. It gives no when-not-to-use or prerequisite guidance.

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