Skip to main content
Glama
gmail-mcp
by gchallen

mark_thread_spam

Destructive

Marks an entire Gmail thread as spam using its thread ID, helping you report unwanted email conversations and reduce inbox clutter.

Instructions

Mark a whole thread as 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>"
    },
    "name": "mark_thread_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond them: it does not say whether messages move out of the inbox, whether existing labels survive, or that the action is reversible via unmark_thread_spam. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the scope qualifier arrives before the action's object. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

The tool is simple and annotations cover the destructive/read-only profile, but for a destructive mutation the description should at minimum note reversibility and the threadId format. Neither is present, and there is no output schema to compensate.

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% and the single parameter threadId is undocumented in both schema and description. The description does not clarify the ID format (thread ID vs message ID), which is the most likely source of an incorrect call given the message-oriented siblings.

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?

"Mark a whole thread as spam" gives a specific verb (mark as spam) and resource (thread), and the qualifier "whole thread" implicitly distinguishes it from the sibling mark_message_spam. It stops short of naming that sibling, so an agent must infer the contrast from the name alone.

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 choose this over mark_message_spam, nor any pointer to unmark_thread_spam for reversal. Usage is only implied by the verb, leaving the agent to infer the thread-vs-message distinction and the undo path.

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