Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

Search outbound messages

search_messages
Read-onlyIdempotent

Locate outbound Postmark messages across one or all accounts and servers by date, status, sender, recipient, subject, stream, or tag; returns IDs, status, recipients, subject, and time.

Instructions

Search outbound messages across all servers (or one). Returns ID, status, recipients, subject, time. Use get_message_details for the delivery event timeline.

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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
countNoMax per server (default 25)
offsetNo
serverNoServer name (partial, case-insensitive), numeric ID, or "account/server". Omit for ALL servers.
statusNo
streamNoMessage stream ID, e.g. outbound
todateNoTo date, YYYY-MM-DD (or YYYY-MM-DDThh:mm:ss)
accountNoAccount name from the accounts file (partial, case-insensitive). Omit for ALL accounts.
subjectNo
fromdateNoFrom date, YYYY-MM-DD (or YYYY-MM-DDThh:mm:ss)
fromemailNoSender email
recipientNoRecipient email (to/cc/bcc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value by specifying the returned fields and the multi-server scoping, but says nothing about pagination behavior, per-server limits, or how 'all servers' aggregation affects result ordering.

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 sentences, zero filler, with scope front-loaded and the sibling redirect placed last. Every clause carries distinct 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?

For a 12-parameter search tool with no output schema, stating the returned fields is a meaningful completion. Defaults such as count=25 per server and the 500 cap are left to the schema, which is acceptable given they are documented there.

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 67%, so structured fields already document most parameters, including the omit-for-ALL semantics for server and account. The description only restates the all-servers-versus-one-server distinction and adds no format or filtering nuance beyond 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?

Names a specific verb and resource ("Search outbound messages") plus the scope ("across all servers (or one)") and enumerates the returned fields. It also distinguishes itself from get_message_details, so an agent can separate it from the sibling without opening schemas.

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?

Explicitly routes the agent to get_message_details when a delivery event timeline is wanted, which is a concrete alternative with a stated condition. It offers no guidance on when to prefer search_bounces or on how to choose among the other siblings, so it stops short of full when/when-not coverage.

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