Skip to main content
Glama
gmail-mcp
by gchallen

unlabel_message

Remove labels from a single Gmail message to archive it, mark it read, or clear custom tags by specifying the message ID and label IDs.

Instructions

Remove labels from one message. Removing INBOX archives it; 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": {
      "messageId": "<messageId>",
      "labelIds": "<labelIds>"
    },
    "name": "unlabel_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdsYes
messageIdYes

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses two non-obvious semantic side effects: removing INBOX archives the message and removing UNREAD marks it read. That is exactly the kind of context annotations cannot convey. It still omits what happens with unknown/absent labels and whether the operation is idempotent.

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 short sentences, zero filler, with the core action front-loaded and the consequence notes immediately after. Nothing could be cut without losing information.

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 two-parameter mutation with no output schema and no parameter documentation, the description covers the key behavioral consequence but not error handling, idempotency, or the response. It is adequate to call the tool correctly in the happy path but incomplete for edge cases.

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 both required parameters. The description only gestures at label semantics by naming INBOX and UNREAD as values, but never says labelIds takes label IDs (not display names), how to obtain them, or what messageId format is expected. With no schema-level documentation, this leaves the parameters largely unexplained.

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?

"Remove labels from one message" gives a specific verb (remove) and resource (labels on a message) with explicit scope, 'one message', which implicitly separates it from thread-level siblings like unlabel_thread. It stops short of naming an alternative, so it is clear but not sibling-differentiating at the highest level.

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: an agent infers this is the tool for stripping existing labels rather than adding them, and the side-effect notes hint at intent (archive/mark read via label removal). There is no explicit when-to-use versus label_message, update_message_labels, or unlabel_thread, and no stated preconditions.

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