Skip to main content
Glama
Sendmux

Sendmux Email Inbox API + Sending

Official

Send Mailbox Message

mailbox_send_message

Send email from an authenticated mailbox, including attachments, CC/BCC, and custom headers. Supports safe retries with an Idempotency-Key.

Instructions

Use this to send a message from the authenticated mailbox. For attachments, call mailbox_upload_attachment first using file_path, presign_upload_url, or tiny content_base64, then pass the returned blob_id. Include an Idempotency-Key for retries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipients.
toNoPrimary recipients.
bccNoBCC recipients.
fromNoSender address. Defaults to mailbox identity.
subjectNoSubject line for the outgoing email.
reply_toNoReply-To recipients.
html_bodyNoHTML body.
text_bodyNoPlain text body.
mailbox_idNoMailbox public ID to target when the credential grants access to more than one mailbox. Omit when the credential is scoped to exactly one mailbox.
attachmentsNoAttachments to send with the message.
custom_headersNoCustom headers to include.
Idempotency-KeyNoClient-chosen unique key to safely retry the request. Cached for 24h per (mailbox, endpoint, key). Different body with same key returns 409 idempotency_conflict.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false. Description appropriately adds context about idempotency key usage for retries and attachment workflow. No contradictions.

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, front-loaded with purpose, then critical workflow. No redundancy or filler.

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?

Given 12 parameters, nested objects, and existing output schema, the description covers essential workflow (attachments, idempotency) without needing to list every parameter. Adequate for agent to invoke 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%, but description adds workflow meaning: attachment parameter requires prior upload, and Idempotency-Key is highlighted for retries. This goes beyond schema details.

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?

Description specifies 'send a message from the authenticated mailbox' with a clear verb and resource. It distinguishes from sibling tools like mailbox_batch_delete_messages, mailbox_list_messages, and sending_send_email by focusing on message sending from the authenticated mailbox.

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?

Provides explicit guidance for attachments (call mailbox_upload_attachment first) and idempotency (include Idempotency-Key). Does not explicitly state when not to use, but the context is clear for sending messages.

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/Sendmux/sendmux-sdk'

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