Skip to main content
Glama
Thestral12

Postfleet MCP

by Thestral12

send_email

Idempotent

Send a new email from a mailbox, idempotent via a unique client_id. If human approval is required, the email is queued as a draft pending approval.

Instructions

Send a new email from one of your mailboxes. Call this when starting a NEW conversation; to answer an email you received, use reply_email instead (it threads correctly). Pass a client_id (any unique string you make up) and reuse the SAME client_id if you retry after an error — that guarantees the email is sent at most once. If the mailbox requires human approval, the send is queued as a draft and returns {draft_id, status:"pending_approval"} instead of a message id — that is NOT a failure and must NOT be retried; the email goes out once a human approves it (check with list_drafts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient email address.
textYesPlain-text body, max 50,000 characters.
subjectYesSubject line, max 200 characters.
client_idYesREQUIRED idempotency key — any unique string you invent for this send. Reuse the SAME value when retrying after an error and the email goes out at most once; a new value sends a second copy. Cannot start with "draft:".
mailbox_idYesId of the mailbox to send from, from list_mailboxes.
Behavior5/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds crucial behavioral details: the client_id guarantees at-most-once delivery, the pending_approval draft response is not a failure, and how to handle that case. 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.

Conciseness5/5

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

Four sentences, each carrying essential information: main action, sibling distinction, idempotency rule, and approval handling. No filler, front-loaded with the primary purpose. Highly efficient.

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?

The description covers purpose, usage, idempotency, and the approval edge case. However, it does not describe the normal success response (e.g., returns a messageId). Since there is no output schema, this is a minor gap. Still, it is largely complete for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100% (all parameters described). The description adds value beyond the schema by explaining the client_id's role as an idempotency key, reuse strategy, and the 'draft:' prefix restriction. It also mentions mailbox_id comes from list_mailboxes. This extra context justifies a 4, as the schema already provides good baseline.

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?

The description starts with 'Send a new email from one of your mailboxes' – a specific verb and resource. It explicitly distinguishes from reply_email by stating when to use each tool (new conversation vs. replying), which differentiates it from siblings.

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 clear when-to-use (starting a new conversation) and when-not-to (use reply_email for replies). Also explains idempotency via client_id reuse and the human approval scenario with specific instructions not to retry and to check list_drafts instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Thestral12/postfleet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server