Skip to main content
Glama
gmail-mcp
by gchallen

apply_sensitive_thread_label

Destructive

Trash or mark an entire Gmail thread as spam via a compatibility alias. Use dedicated trash_thread or mark_thread_spam tools instead.

Instructions

Compatibility alias for the official server: TRASH or SPAM a whole thread. Prefer trash_thread / mark_thread_spam.

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>",
      "labelOption": "<labelOption>"
    },
    "name": "apply_sensitive_thread_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes
labelOptionYes

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 destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds the meaningful scope detail that the destructive effect covers an entire thread and flags the tool as a legacy/compatibility path. It does not mention reversibility (untrash_thread/unmark_thread_spam exist as siblings) or that the label is applied rather than the thread being purged.

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: identity and effect first, then the preferred alternatives. Every clause carries information and nothing is padded.

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?

A destructive two-parameter tool with annotations covering the safety profile and no output schema needs little prose, and the alias status plus the alternative routing cover the essentials. Gaps remain around reversibility and the distinction between the two label options, which an agent would otherwise have to guess.

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% over two required parameters, yet the description only echoes the labelOption enum values (TRASH/SPAM) that the schema already enumerates. threadId is never characterized, and the differing consequences of TRASH versus SPAM are not explained, so the text does little to compensate for the coverage gap.

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 ('TRASH or SPAM a whole thread') and frames the tool as a compatibility alias for the official server, which distinguishes it from the native siblings. It falls short of 5 only because the alias framing is compressed into a single phrase rather than explaining what compatibility means in practice.

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

Usage Guidelines4/5

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

Explicitly routes the agent away from this tool by naming the preferred alternatives ('Prefer trash_thread / mark_thread_spam'). What is left implicit is the positive condition for using this one, namely that the caller must be bound to the official server's tool names.

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