Skip to main content
Glama
egyptianego17

email-mcp-server

send_custom_email

Send a custom email with full configuration including recipients, subject, body (plain text or HTML), attachments, and optional SMTP settings.

Instructions

Send a custom email with full configuration options.

    Args:
        email: Email message details including:
            - to: Recipient email address(es) (string or list)
            - cc: CC email address(es) (optional, string or list)
            - bcc: BCC email address(es) (optional, string or list)
            - subject: Email subject
            - text: Plain text email body (optional)
            - html: HTML email body (optional)
            - attachments: List of attachments (optional), each with:
                - path: Local file path to attach (preferred)
                - content: Base64-encoded file content (alternative to path)
                - filename: Override filename (auto-derived from path if omitted)
                - mime_type: MIME type override (optional)
        smtp_config: Optional SMTP configuration override with:
            - host: SMTP server hostname
            - port: SMTP server port
            - secure: Use SSL/TLS
            - username: Auth username
            - password: Auth password
            - from_email: Sender email address

    Returns:
        Success message or error message
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes
smtp_configNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full behavioral burden. It discloses the return type (success or error message) and elaborates on parameters, but does not mention authorization needs, rate limits, or side effects beyond the act of sending. Adequate but not thorough.

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?

The description is well-structured with a concise purpose sentence followed by detailed Args and Returns sections. However, it is somewhat verbose for the parameter details; could be more terse while maintaining completeness. Barely loses a point for efficiency.

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?

Given the tool has nested objects, no schema descriptions, and an output schema (implied), the description provides thorough coverage of all parameter structures, optionality, and return behavior. It fully compensates for the schema's lack of descriptions.

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?

Schema description coverage is 0%, so the description must compensate, and it does excellently. It details the email object with nested fields (to, cc, bcc, subject, text, html, attachments with subfields) and smtp_config (host, port, secure, username, password, from_email), adding meaning like 'preferred' and 'auto-derived' that the schema lacks.

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 'Send a custom email with full configuration options,' which precisely specifies the verb and resource. It distinguishes from siblings (send_simple_email, test_smtp_connection) by emphasizing 'full configuration' and 'custom,' implying this tool is for advanced scenarios.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies it's for complex email needs via 'full configuration,' but it does not mention when-not-to-use or directly compare to send_simple_email. Slight gap in intentionality.

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

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