Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

Search bounces

search_bounces
Read-onlyIdempotent

Search Postmark bounces across all or one server using email, type, date, and deactivation filters to find delivery failures and failed sends.

Instructions

Search bounces across all servers (or one).

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": "search_bounces"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoBounce type, e.g. HardBounce, SoftBounce, SpamComplaint
countNoMax per server (default 25)
emailNoFilter by email (partial match)
serverNoServer name (partial, case-insensitive), numeric ID, or "account/server". Omit for ALL servers.
todateNoTo date, YYYY-MM-DD (or YYYY-MM-DDThh:mm:ss)
accountNoAccount name from the accounts file (partial, case-insensitive). Omit for ALL accounts.
fromdateNoFrom date, YYYY-MM-DD (or YYYY-MM-DDThh:mm:ss)
inactiveNoOnly bounces that deactivated the address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the cross-server scope note; it says nothing about result volume across many servers, the per-server cap, or pagination behavior, which would be the valuable additions here.

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?

A single front-loaded sentence with zero filler and no repetition of schema content. It is efficient, though the terseness leaves little room for the routing or volume context an agent would benefit from.

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?

With 8 optional parameters fully documented in the schema and complete annotations, the description only needs to cover scope and result shape. It handles scope but omits that results are gathered per server (so an unscoped search may return data from many servers) and gives no sense of return structure, leaving a gap for a broad search tool.

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 all eight parameters (type, email, server, account, dates, inactive, count) are already documented in the schema. The description's 'across all servers (or one)' echoes the server parameter's own description without adding format or interaction detail, so 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?

The description gives a specific verb and resource ('Search bounces') plus a scope qualifier ('across all servers (or one)'), so an agent immediately knows what is returned. It stops short of naming a distinguishing feature versus siblings such as search_messages or list_suppressions, but the resource noun alone is reasonably discriminative.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives or exclusions. The only hint is the parenthetical about server scope, which restates a parameter rather than explaining when this tool is the right choice over delivery_stats or list_suppressions.

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