Skip to main content
Glama

Check addresses against my unsubscribe list

suppression_check
Read-only

Before sending: which of these addresses are on your unsubscribe list (unsubscribed, bounced, complained or added by you); case does not matter. Each result has suppressed and, when true, reason, source and since: skip those. Non-addresses come back not_an_address. Changes nothing. Then unsubscribe_links for the others.

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",
        "team@example.org"
      ],
      "instance_id": "sup_exampleexampleexample2"
    },
    "name": "suppression_check"
  }
}

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",
      +      "team@example.org"
      +    ],
      +    "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.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false; the description goes beyond them by describing the return shape (suppressed, plus reason/source/since when true), the invalid-input outcome (not_an_address), and case-insensitive matching. Since there is no output schema, this disclosure of result fields and the 'skip those' decision rule is exactly the missing behavioral context.

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 triggering condition and then the result contract, with almost no wasted words. 'Changes nothing' is largely redundant with readOnlyHint and the telegraphic phrasing takes a moment to parse, but the density is deliberate and useful.

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 read-only, three-parameter lookup with no output schema, the description covers purpose, timing, result fields, invalid input, and the follow-up tool — enough to call it correctly. It leaves error behavior and any batching/rate implications unstated, but the schema already carries the 1000-address cap.

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 real meaning for the emails parameter: matching is case-insensitive and non-address strings are reported rather than erroring. It does not add anything for instance_id or passport_token beyond what the schema already documents.

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 — checks whether given addresses appear on the caller's unsubscribe list — and enumerates the four suppression categories (unsubscribed, bounced, complained, added by you). This clearly separates it from the suppression_add/remove/export siblings and from check_emails, and the follow-up pointer to unsubscribe_links further anchors its role.

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?

The opening 'Before sending:' gives an explicit trigger condition, and 'Then unsubscribe_links for the others' routes the agent to the correct next tool for non-suppressed addresses. It does not explicitly exclude the deliverability-oriented check_emails sibling, so the agent still has to infer which check applies, but the timing guidance is unambiguous.

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.