Skip to main content
Glama

Add addresses to my unsubscribe list

suppression_add
Idempotent

Add your own addresses to your unsubscribe list (stored as keyed hashes); unsubscribes through your links join it by themselves. keep_address true also keeps them sealed so suppression_export gives them back. At most 50,000 per list, all or nothing; a listed address keeps its reason (already_listed). Undo: suppression_remove.

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": "bounce",
      "instance_id": "sup_exampleexampleexample2"
    },
    "name": "suppression_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesPlain addresses, up to 1000.
reasonNoWhy (default manual).
instance_idYesUtility instance id from buy or list_utilities.
keep_addressNoAlso keep the address sealed for export (default false: hash only).
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": "bounce"
      +  }
      +]
    • 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.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses key behavior: addresses are stored as keyed hashes, link-driven unsubscribes are added automatically, keep_address enables export via suppression_export, and duplicate addresses retain their reason as already_listed. It also states the 50,000-per-list cap and all-or-nothing semantics, which materially affect how an agent should invoke it.

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 description is dense and front-loads the core purpose, storage model, and key constraints. Some phrasing is compressed to the point of terseness, such as 'all or nothing' and 'keeps them sealed,' but there is little wasted text.

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?

For a mutation tool without an output schema, it covers the important operational facts: hashing, export behavior, list cap, atomicity, duplicate handling, and undo path. It does not describe the response shape or batching strategy beyond the schema's 1000-item limit, but the critical behavioral context is present.

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, but the description adds meaning beyond the schema by explaining keep_address's export consequence and the duplicate reason behavior. It does not add detail for instance_id or passport_token, but those are already well described in the schema.

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 states a specific action and resource: adding addresses to 'your unsubscribe list.' It also distinguishes this manual path from link-driven unsubscribes that 'join it by themselves,' and it names suppression_export and suppression_remove for related operations.

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 clearly frames this as the manual way to add addresses and points to suppression_remove as the undo. It does not explicitly say when to use suppression_check or how this compares with suppression_settings, so some sibling routing is left implicit.

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.