Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

Delivery stats

delivery_stats
Read-onlyIdempotent

Retrieve outbound delivery metrics per Postmark server—sent, bounced, bounce rate, spam complaints, opens, and clicks—to monitor email performance and identify issues.

Instructions

Outbound overview per server: sent, bounced, bounce rate, spam complaints, opens, clicks.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
serverNoServer name (partial, case-insensitive), numeric ID, or "account/server". Omit for ALL servers.
streamNo
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 real value by enumerating the returned metrics, which is important given there is no output schema, but it says nothing about default date range, aggregation granularity, or result size.

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 compact sentence with no wasted words and the resource front-loaded. It is a fragment without an explicit verb, but nothing is redundant.

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?

For a 6-parameter reporting tool with no output schema, the metric list usefully stands in for return-value documentation. However, missing guidance on tag/stream, date-range defaults, and whether results are grouped by day or server leaves the agent guessing on key invocation choices.

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?

At 67% schema coverage the schema documents server, account, fromdate and todate well, but tag and stream remain undocumented in both places. The description contributes only the phrase 'per server', which hints at grouping; it does not compensate for the undocumented parameters or explain date defaults.

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 a specific resource and scope: outbound delivery metrics aggregated per server, enumerating the metrics returned (sent, bounced, bounce rate, spam complaints, opens, clicks). The aggregate/overview framing implicitly distinguishes it from message-level siblings like search_messages and get_message_details, though no sibling is named.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied by the word 'overview' and the 'per server' aggregation, leaving the agent to infer that this is for summary reporting rather than per-message lookup.

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