Skip to main content
Glama

Take addresses off my unsubscribe list

suppression_remove
DestructiveIdempotent

Take addresses off your unsubscribe list, with a reason (resubscribed, added_by_mistake, bounce_resolved, other). Someone who unsubscribed or complained comes off only with resubscribed (they asked to hear from you again). Recorded; removed addresses may get your mail again. Each result: removed, or why not (not_listed, not_an_address, ..._needs_resubscribed). To look before sending: suppression_check.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emails": [
        "reader@example.com"
      ],
      "reason": "resubscribed",
      "instance_id": "sup_exampleexampleexample2"
    },
    "name": "suppression_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesPlain addresses, up to 1000.
reasonYesWhy they come off.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "emails": [
      +      "reader@example.com"
      +    ],
      +    "instance_id": "sup_exampleexampleexample2",
      +    "reason": "resubscribed"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Given destructiveHint=true and idempotentHint=true in annotations, the description still adds the consequential fact that removed addresses may receive mail again, plus per-item result semantics ('removed, or why not') and reason-dependent behavior (unsubscribed/complained contacts only come off with resubscribed). That is substantive disclosure beyond the annotation set.

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?

Front-loaded with the core action, then constraints, then results, then the alternative — logical ordering with no filler. The telegraphic semicolon phrasing ('Recorded; removed addresses may get your mail again') is dense but slightly clipped.

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?

With no output schema, the description carries the return-value burden and does so by enumerating result states (removed / not_listed / not_an_address / ..._needs_resubscribed). Combined with the reason constraint and the preview alternative, an agent has what it needs to call this destructive operation correctly.

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 baseline is 3; the description exceeds it by explaining what the reason enum values mean operationally and which one is mandatory for previously unsubscribed or complaining addresses, which the schema enum alone does not convey.

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 concrete verb+resource ('take addresses off your unsubscribe list') and immediately names the sibling to use for inspection (suppression_check), so the agent can separate it from suppression_add/check without opening a schema.

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?

Gives an explicit pre-flight alternative ('To look before sending: suppression_check') and a hard usage rule for the resubscribed reason. It does not explicitly contrast with suppression_add or state when a removal should be attempted at all, so it stops short of full when/when-not guidance.

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.