Skip to main content
Glama
Sign In
Email MCP Server

Email MCP Server

by 123jixinyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

send_email

Send new emails with plain text or HTML content, supporting CC, BCC, and file attachments. Compose and deliver messages directly from your account.

Instructions

Send a new email. Supports plain text or HTML body, CC, and BCC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC recipients
toYesRecipient email addresses
bccNoBCC recipients
bodyYesEmail body content
htmlNoSend as HTML (default: plain text)
accountYesAccount name from list_accounts
subjectYesEmail subject
attachmentsNoLocal files to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate this is a mutating operation (readOnlyHint=false, openWorldHint=true). The description confirms the action of sending but adds no additional behavioral context such as whether the send is synchronous, whether confirmation is returned, or any side effects beyond actually sending. With annotations covering the basic write nature, a score of 3 reflects minimal added transparency.

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?

One succinct sentence that front-loads the main action, then lists the key supporting features. Every word contributes to understanding, with no 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 eight parameters and no output schema, the description is adequate to understand the tool's core purpose and key options. It doesn't cover return behavior or prerequisites beyond the schema, but for a straightforward send action with good schema coverage, it meets the minimum and is slightly better due to clear scope.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds little beyond repeating that CC and BCC are supported and mentioning HTML body, but does not provide format details, syntax, or relationships beyond what the schema already documents.

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 uses the specific verb 'Send' and names the resource 'a new email', clearly distinguishing from siblings like reply_email, forward_email, and save_draft by emphasizing 'new'. It also mentions key format options (plain text/HTML, CC, BCC), making the purpose unambiguous.

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?

The description implies usage for new outgoing emails by the phrase 'a new email', but it does not explicitly state when not to use it or name alternatives like reply_email, forward_email, or schedule_email. There is no when/when-not guidance, so it falls at implied usage.

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

Deploy Server

Other Tools