PostAgent

Upload a finished letter (identical content, no mail merge)

create_letter

Upload and normalize a FINISHED, ready-to-mail document to PDF. Choose this when the content is final and IDENTICAL for every recipient — including when you mail the same letter to many people (just quote/pay once per recipient with the same documentId). The exact bytes you give are what gets printed. Use create_template instead only when the content must vary per recipient via {{fields}}. Returns a documentId, the stored page count, byte size, and source format. Free; no payment required.

Provide the document EXACTLY ONE way: content (inline text, for html/markdown/text), contentBase64 (base64-encoded binary, for pdf/docx/image), or url (a publicly reachable URL the server fetches). Supplying none, or more than one, is an error. Maximum upload size is 31457280 bytes (~30 MB); output page size is US Letter.

Any {{...}} text is printed LITERALLY here — it is NOT treated as a merge field. If you want personalized mail merge across recipients, use create_template instead.

Reserved address zone: a recipient address block is printed over the top ~3 inches of page 1, so the server reserves that space for you automatically. For text/html/markdown/docx, page-1 content is pushed below the block (content may therefore flow onto an additional page); for pdf and image inputs, a blank first page is prepended. As a result the returned page count — and the selected-provider cost behind the resulting quote — can be higher than your source document (e.g. a single-page PDF is stored as 2 pages). You do NOT need to leave the top of your document blank yourself. See the postagent://formats resource for per-format details.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Public URL the server will fetch the document from. Provide exactly one source.
`format`	No	Source format. Inferred from contentType/filename/content when omitted; inline `content` with no format defaults to text.
`content`	No	Inline text content (html, markdown, or text). Provide exactly one source.
`filename`	No	Optional original filename; used to help infer the source format.
`contentBase64`	No	Base64-encoded binary content (pdf, docx, image). Provide exactly one source.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJun 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds substantial context beyond annotations: upload and normalize behavior, reserved address zone, page count increase for PDF/images, literal {{...}} handling, upload size limit, and source exclusivity. No contradictions with annotations.

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?

Well-structured with front-loaded purpose. Each paragraph adds necessary detail, though slightly verbose. Could be more concise but remains clear and informative.

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

Completeness5/5

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

Complete for a tool with no output schema: describes return fields (documentId, page count, byte size, source format). Covers all edge cases (source exclusivity, size limit, address zone, page count increase) and references external resource for format details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds critical semantics beyond schema: exactly one source required (content, contentBase64, or url), mutual exclusivity constraint not in schema, format inference defaults, and max upload size. Enhances understanding despite 100% schema coverage.

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?

Clearly states uploading a finished, identical letter for all recipients. Explicitly distinguishes from create_template for mail merge. Verb 'upload' and resource 'finished letter' are precise.

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

Usage Guidelines5/5

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

Provides explicit when-to-use (final, identical content) and when-not (use create_template for variable content). Includes context like free, no payment needed, and explains reserved address zone behavior.

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

All PostAgent tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a distinct function: updates, document upload (letter/template/postcard), quoting (single, campaign, postcard), payment (x402, MPP, card checkout, detached signature), and status tracking. There is minimal overlap; even the three quote tools (create_mail_quote, create_campaign_quote, create_postcard_quote) are clearly differentiated by recipient type and workflow.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_letter, get_campaign_status, submit_paid_mail_job). Verbs are descriptive and nouns clearly indicate the resource or action. There are no mixed conventions or vague names.

Tool Count5/5

14 tools is well-scoped for a mailing and payment server. Each tool serves a distinct step in the workflow (upload, quote, pay, verify, track) without redundancy. The count is neither too low (would miss essential operations) nor too high (would overwhelm).

Completeness4/5

The tool set covers the core lifecycle: document preparation, quoting, multiple payment rails, address verification, and status tracking. Minor gaps exist, such as no explicit tool to cancel a job or list previously created documents, but these are not critical for typical use and can be worked around.

Resources

Need Help?