Skip to main content
Glama
gmail-mcp
by gchallen

apply_sensitive_message_label

Destructive

Marks a single Gmail message as trash or spam using message ID and label option. Compatibility alias for the official Gmail MCP server actions.

Instructions

Compatibility alias for the official server: TRASH or SPAM one message. Prefer trash_message / mark_message_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": {
      "messageId": "<messageId>",
      "labelOption": "<labelOption>"
    },
    "name": "apply_sensitive_message_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes
labelOptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4.2/5.0
Behavior4/5

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

Adds context beyond the annotations: it is a compatibility alias (so behavior may be legacy), and it affects exactly one message (no batch semantics). The destructive nature is already declared by destructiveHint=true, so the description needn't restate it, though it could note irreversibility of TRASH/SPAM more explicitly.

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 clauses, with the action stated first and the alternative-tool routing second. No filler whatsoever.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter alias with a destructive annotation and no output schema, the description supplies the essential facts: what it does, that it is single-message, and that preferred alternatives exist. Only the messageId format is left unexplained, which is minor.

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 carries some burden; it clarifies that labelOption is TRASH or SPAM (already visible in the enum) but says nothing about the messageId format or expected identifier source. Partial compensation warrants a minimum-viable score.

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 concrete action (TRASH or SPAM one message) and identifies itself as a compatibility alias, which is the key fact distinguishing it from the canonical siblings. It is slightly indirect because the tool's name says 'label' while the description says 'trash/spam', but the clarification resolves that.

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

Usage Guidelines5/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 with 'Prefer trash_message / mark_message_spam', naming both alternatives and implying this should only be used for compatibility reasons. That is precisely the when-not-to-use guidance an agent needs.

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