Skip to main content
Glama

messages_unsubscribe

Destructive

Unsubscribe from the mailing list an e-mail message came from, using the sender's own List-Unsubscribe header: a one-click request when offered, else an unsubscribe e-mail sent from the same mailbox. A plain web link is returned, never opened automatically. Works on mailboxes connected over IMAP/SMTP; other channels refuse. The answer says which method was used and the sender's HTTP status.

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": {
      "message_id": "<message_id>"
    },
    "name": "messages_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesID of a message from the mailing list (from messages.read_history).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructive, open-world, non-idempotent, and non-read-only behavior, but the description adds substantial operational detail beyond them. It explains the List-Unsubscribe mechanism, the one-click versus email fallback, that the email is sent from the same mailbox, that a returned web link is not opened automatically, the channel restriction, and what the response reports.

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?

Four sentences, front-loaded with the action and mechanism, with each sentence adding useful operational information: method selection, link handling, channel constraint, and response content. There is no filler.

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?

No output schema exists, but the description sufficiently indicates the response includes which method was used and the sender's HTTP status. It does not describe what happens if the message has no List-Unsubscribe header or if authentication fails, which is a modest gap for a destructive open-world tool.

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 100%, and the schema already documents both message_id and in_workspace. The description adds no parameter-specific syntax or meaning beyond the schema's own explanation that the message must come from a mailing list.

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?

States a specific verb and resource: unsubscribe from the mailing list a message came from. The mechanism, using the sender's List-Unsubscribe header, distinguishes it clearly from generic sibling tools such as messages_delete or messages_send.

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

Usage Guidelines4/5

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

Explains the relevant context (message from a mailing list) and an explicit exclusion (only IMAP/SMTP mailboxes work; other channels refuse). It also describes the one-click-versus-email fallback, but does not name an alternative tool or explicitly distinguish when to delete/archive the message instead.

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.