Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

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 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.

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
Behavior5/5

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

Annotations already declare readOnly/non-destructive, but the description adds real behavioral facts: nothing is stored, links are deterministic per address, the address is never exposed in the link. It also names the two result markers (not_an_address, suppression_no_address) that an agent would otherwise not know.

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?

Three dense sentences with the core capability front-loaded and no filler. Density is high but every clause carries a distinct fact; slightly more structural separation of the output markers would improve scanability.

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 still conveys the return shape (Links one per recipient plus the header pair, and the two edge-case markers). It stops short of stating the exact response field layout, but an agent has enough to call and interpret it correctly.

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% and already documents instance_id provenance and the 1000-address limit. The description only adds meaning to the emails field by explaining that non-address entries are flagged rather than failing, which is a marginal gain over 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?

States a specific verb and resource ('Signed one-click unsubscribe links ... one per recipient') plus the deliverable (the exact List-Unsubscribe and List-Unsubscribe-Post headers). An agent can distinguish this from suppression_add/check/export siblings purely from the text.

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

Usage Guidelines3/5

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

Implies usage ('for your unsubscribe-list', 'headers to add to that email') and clarifies it only computes rather than stores, which shapes when to call it. However, it never names the alternatives (suppression_add, suppression_check, suppression_export) or states when-not to use it, leaving the agent to infer boundaries.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources