Skip to main content
Glama
gmail-mcp
by gchallen

mark_message_spam

Destructive

Marks a specified Gmail message as spam by adding the SPAM label and removing it from INBOX. Use it to flag unwanted email by message ID.

Instructions

Mark one message as spam (adds SPAM, removes 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": "mark_message_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description does add real value by naming the exact state change (SPAM added, INBOX removed), but it omits reversibility, idempotency for already-spammed messages, and any 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 effect stated immediately after the action; no wasted wording.

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 mutation tool with annotations covering destructiveness, the definition is nearly complete: the state change is explicit. Only the idempotency/reversibility behavior and messageId format are left unstated.

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% for the single messageId parameter, so the description carries the burden but says nothing about it. Since messageId is a self-evident identifier, the gap is minor but real.

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?

The description gives a specific verb ('mark') and resource ('one message') plus the concrete effect (adds SPAM, removes INBOX). The phrase 'one message' implicitly separates it from mark_thread_spam, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over mark_thread_spam, trash_message, or unmark_message_spam, and no mention of prerequisites or preconditions. Usage is only inferable from the parenthetical effect.

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