Skip to main content
Glama
ai-zerolab

MCP Email Server

by ai-zerolab

save_to_mailbox

Compose and save an email to an IMAP folder (e.g., Drafts) with recipients, subject, body, attachments, and flags. Useful for drafting emails without sending.

Instructions

Compose an email and save it to an IMAP folder (e.g., Drafts). Same parameters as send_email, but saves instead of sending. Default folder is Drafts with \Draft and \Seen flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_nameYesThe name of the email account.
recipientsYesA list of recipient email addresses.
subjectYesThe subject of the email.
bodyYesThe body of the email.
mailboxNoThe IMAP folder to save to (e.g., 'Drafts', 'INBOX.Drafts', 'Templates').Drafts
ccNoA list of CC email addresses.
bccNoA list of BCC email addresses.
htmlNoWhether the email body is HTML (True) or plain text (False).
attachmentsNoA list of absolute file paths to attach to the email.
in_reply_toNoMessage-ID of the email being replied to. Enables proper threading in email clients.
referencesNoSpace-separated Message-IDs for the thread chain.
flagsNoIMAP flags to set on the message. Defaults to ['\\Draft', '\\Seen']. Common flags: '\\Draft', '\\Seen', '\\Flagged'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses saving behavior and default flags, but omits details about side effects, authentication, rate limits, or error handling.

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?

Three concise sentences front-load the core purpose and key differentiator; every sentence adds essential information without redundancy.

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?

Covers the primary use case, comparison to send_email, and defaults. Could mention that the account must exist (related to the add_email_account sibling) but is generally sufficient for a parameter-rich tool.

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 100%, so baseline is 3. Description adds minimal new parameter info beyond the schema (e.g., default folder mention), not enough to raise the score.

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 clearly states the tool composes an email and saves it to an IMAP folder, distinguishing it from the sibling send_email by contrasting 'saves instead of sending'.

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 references send_email as the alternative for sending, and notes default folder and flags. However, it does not mention other sibling tools or conditions like account pre-configuration.

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/ai-zerolab/mcp-email-server'

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