Skip to main content
Glama
gmail-mcp
by gchallen

unmark_message_spam

Removes a Gmail message from Spam and restores it to the inbox by message ID, helping recover legitimate mail that was incorrectly flagged.

Instructions

Un-spam one message (removes SPAM, restores INBOX).

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

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds the concrete mutation semantics (SPAM label removed, INBOX restored), which is genuine value beyond the annotations. It stops short of covering idempotency, what happens if the message is not currently spam, or permission requirements.

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 action first and the resulting state in parentheses. No filler or redundant restatement of the tool name.

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 one-parameter label toggle with annotations present and no output schema, the description says enough to invoke it correctly. Only edge-case behavior (already-unspammed messages, error responses) is absent.

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 the burden, and it only conveys that a single message is targeted. The name messageId is largely self-explanatory, but no ID format or accepted prefix is given to compensate for the undocumented schema.

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 ("Un-spam one message") and spells out the resulting state change ("removes SPAM, restores INBOX"). The phrase "one message" implicitly separates it from the thread-level sibling, though no sibling is named outright.

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 scope word "one message"; there is no explicit statement of when to use this versus unmark_thread_spam, mark_message_spam, or label-based alternatives. An agent can infer the intent, but nothing routes it deliberately.

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