Skip to main content
Glama

Report a thread as spam

report_spam

Moves a thread of a mailbox into its Spam folder, where it stays readable and can be taken back out, and blocks its sender: their next message is filed in Spam too, without anybody being asked again. Spam is emptied 30 days after a thread lands there by default, or after the retention set on the account, and that deletion is final. Threads of a helpdesk queue have no Spam folder and are refused: file_conversation with "trash" throws them away instead. To report several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "report_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesThe id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: spam remains readable and reversible, the sender is blocked on future messages, retention is 30 days by default or account setting, and the eventual deletion is final. Batch failure semantics – per-thread results in 'results', 'succeeded'/'failed' counts, partial success, and error only when none succeed – are also disclosed.

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?

The core action and its consequences are front-loaded, then retention, refusal, and batching follow in a logical order. It is dense and long for a single-paragraph description, but nearly every clause adds decision-relevant information rather than restating the name.

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

Completeness5/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 no output schema, the description covers the mutation, its reversibility, its retention horizon, the refusal case, and the shape of the batch response. Nothing an agent needs in order to call it safely and interpret results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents the string-or-array shape and the 50-id cap, so the baseline is met by the schema. The description adds real meaning beyond it: the id comes from list_conversations, and the list form triggers per-thread outcomes in the response, which an agent would not infer from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Moves a thread of a mailbox into its Spam folder') plus the side effect ('blocks its sender'), which separates it from siblings like mark_not_spam and file_conversation. An agent knows exactly what the tool does without opening the schema.

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?

It names when this tool applies, explicitly redirects helpdesk-queue threads to file_conversation with 'trash', and instructs to batch multiple ids into ONE call instead of one call per thread. Both the alternative and the alternative's condition are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources