Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

List suppressions

list_suppressions
Read-onlyIdempotent

List suppressed recipients by server, stream, or account to check hard bounces, spam complaints, and manual suppressions, or verify an exact email address.

Instructions

Suppressed recipients per server/stream (hard bounces, spam complaints, manual). Omit server for all servers; omit stream for all streams.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_suppressions"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoExact email to check
serverNoServer name (partial, case-insensitive), numeric ID, or "account/server". Omit for ALL servers.
streamNoMessage stream ID (default: every stream of the server)
accountNoAccount name from the accounts file (partial, case-insensitive). Omit for ALL accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are partitioned by server/stream and enumerates suppression sources, but says nothing about result volume, pagination, or ordering — relevant for a listing tool that can span all accounts and servers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the scope statement front-loaded and the omission rules paired compactly. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four parameters are optional and zero-required, and annotations fully cover the read-only safety profile, but there is no output schema, so the agent gets no hint about what a suppression record contains (reason, timestamp, scope) or how large unfiltered results will be. That is a meaningful gap for a list tool that defaults to all accounts and all servers.

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 description coverage is 100%, so every parameter, including the account and email filters, is already documented in the schema. The description only restates the omit-for-all behavior for server and stream, adding no new semantics over the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource ('Suppressed recipients') and its scoping axes (per server/stream) plus the categories that produce a suppression (hard bounces, spam complaints, manual), so an agent understands this returns suppression records rather than raw bounce events. It does not explicitly contrast itself with search_bounces, leaving the sibling distinction to be inferred.

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?

The description gives scoping guidance ('Omit server for all servers; omit stream for all streams'), which is really parameter usage rather than when-to-use guidance. It never says when to choose this over search_bounces or delivery_stats, so tool selection is only implied by the resource name.

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