Skip to main content
Glama

Make signed unsubscribe links

unsubscribe_links
Read-only

Signed one-click unsubscribe links for your unsubscribe-list, one per recipient, with the exact List-Unsubscribe and List-Unsubscribe-Post headers to add to that email. Only computes them: nothing about the recipients is stored, the same address in any letter case always gets the same link, and a link never shows the address. Entries that are not addresses are marked not_an_address; when none is an address the answer is suppression_no_address. Put them in every email: an unsubscribe through one joins the list by itself; suppression_check finds it before the next send.

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"
      ],
      "instance_id": "sup_exampleexampleexample2"
    },
    "name": "unsubscribe_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesPlain addresses, up to 1000.
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"
      +  }
      +]
    • 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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces rather than contradicts this by stating 'Only computes them: nothing about the recipients is stored' — a genuinely useful guarantee beyond the annotation. It also discloses determinism ('same address in any letter case always gets the same link'), privacy behavior ('a link never shows the address'), and per-entry error markers (not_an_address, suppression_no_address). Missing only things like rate limits or what the success payload looks like.

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?

Dense and front-loaded: the core capability and its output (headers) come first, then behavioral guarantees, then error markers, then workflow advice. Some colons-and-fragments phrasing ('Only computes them:', 'Put them in every email:') reads as clipped, but almost every clause carries information.

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?

With no output schema, the description does the needed work by describing what is returned (per-recipient links plus exact header names) and how non-address and all-invalid inputs are signaled. For a 3-parameter, side-effect-free tool this is close to sufficient; only the concrete response shape remains unspecified.

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 coverage is 100%, so each parameter's meaning is already documented in the schema. The description adds the useful syntactic implication of 'one per recipient' (parallel output per input address), but says nothing extra about instance_id or the passport_token fallback path, so it stays at the baseline.

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?

Names a specific verb+resource: generates signed one-click unsubscribe links, one per recipient, plus the exact List-Unsubscribe and List-Unsubscribe-Post headers. It is immediately distinguishable from the sibling suppression_check, which it explicitly positions as the downstream lookup step.

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 a clear directive on when to use it ('Put them in every email') and explains the workflow linkage: an unsubscribe through one joins the list by itself, and suppression_check finds it before the next send. No explicit exclusion cases or failure-mode guidance for calling it, so not a full 5.

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.