Skip to main content
Glama
Sign In
Timbre

Timbre

by alejandrosml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

unsubscribe

Idempotent

Leave a newsletter or mailing list by selecting one of its messages. Opt out in one click when the sender supports it; otherwise open the sender's page or ready email.

Instructions

Leave a newsletter or mailing list, given one of its messages (mail_stats lists them). In one click when its sender offers it and the receiving server confirmed the sender: a window on the Mac asks the user first, as it cannot be undone. Otherwise the page to open (open: true opens it in the browser) or a ready e-mail the user sends.

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": {
      "id": "<id>"
    },
    "name": "unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA message from the newsletter or list (mail_stats gives the latest of each).
openNoWhen the sender only offers a web page: open it in the user's browser.

Output Schema

NameRequiredDescriptionDefault
viaNoThe page or address the request goes to.
noteYes
senderYes
statusYesunsubscribed, awaiting_approval, cancelled, link, opened or draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A3.8/5.0
Behavior1/5

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

The description reveals useful behavior: one-click unsubscribe only when the sender offers it and the receiving server confirmed the sender, a Mac confirmation window, and fallback page/email paths. However, it explicitly says the action 'cannot be undone' while the annotations set destructiveHint=false, creating a direct safety-profile conflict.

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 purpose is front-loaded and the description is compact with no filler. The fallback sentence is slightly elliptical and technical, but overall it remains efficient.

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 two-parameter action with an output schema and annotations, the description covers the important invocation paths, the confirmation step, sender verification, and fallback behavior. An agent has enough information to call it correctly aside from the annotation conflict noted above.

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%, so the schema already documents both parameters. The description still adds context by identifying mail_stats as the source for id and by clarifying that open:true opens the fallback web page in the browser.

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 gives a specific verb and resource: 'Leave a newsletter or mailing list, given one of its messages.' It also points to mail_stats for finding the required message id, making the purpose and input source clear.

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?

It explains when the tool applies and how to get the required id from mail_stats, and it distinguishes the one-click path from the page/email fallback paths. It does not explicitly state when not to use the tool or name a direct alternative, so it falls short of a 5.

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

Deploy Server

Other Tools