Skip to main content
Glama
rosauceda

cpanel-mail-mcp

by rosauceda

send_email

DestructiveIdempotent

Send emails with HTML, attachments, and save-to-sent support. Use idempotency keys to prevent duplicate delivery on retries.

Instructions

Send an email. Supports HTML, attachments, and Save-to-Sent.

On retries after a client timeout, pass the same idempotency_key you used the first time to prevent duplicate delivery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toYesRecipient(s), comma-separated.
bccNo
htmlNoHTML body; sent as multipart/alternative when both are set.
textNoPlain-text body.
accountNo
confirmNoSend-gate code if EMAIL_SEND_CONFIRMATION_CODE is set.
subjectNo
reply_toNo
attachmentsNo[{path|content|content_base64, name?, mime?}, ...]
save_to_sentNoOverride the account's Save-to-Sent default.
idempotency_keyNoOpaque key; identical (key, caller) within 5 min returns the cached result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
accountYes
message_idNo
recipientsYes
saved_to_sentNo
idempotent_replayNoTrue when this response was replayed from an earlier identical call within the idempotency window.
Behavior4/5

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

Beyond annotations (readOnly=false, destructiveHint=true, idempotentHint=true), the description adds valuable behavioral context: supports HTML, attachments, Save-to-Sent, and retry idempotency. It does not cover all side effects (e.g., irreversible send) but adds meaningful info.

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?

The description is concise: three sentences that front-load the purpose and then add key details. No unnecessary words.

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?

Given the tool's complexity (12 params, 1 required, many siblings), the description covers main features and retry behavior but lacks usage guidelines and full parameter semantics. Annotations fill some gaps, but completeness is average.

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?

With 58% schema description coverage (7 of 12 params documented), the description adds extra context for html, attachments, save_to_sent, and idempotency_key. However, many parameters (cc, bcc, reply_to, text, account, confirm) are not addressed, so the description only partially compensates for schema gaps.

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 clearly states the verb 'Send' and resource 'email', and highlights key features (HTML, attachments, Save-to-Sent). This distinguishes it from sibling tools like send_invite, reply_email, or forward_email.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives such as reply_email, forward_email, or send_invite. The description only hints at retry behavior but not comparative usage.

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/rosauceda/cpanel-mail-mcp'

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