Skip to main content
Glama
AWS SES MCP Server

AWS SES MCP Server

Send Email

send_email

Send emails through AWS SES with recipient, subject, and HTML or plain-text body, plus optional CC, BCC, and sender address.

Instructions

Send an email using AWS SES.

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC recipients, comma-separated.
toYesRecipient email address.
bccNoBCC recipients, comma-separated.
bodyYesEmail body (HTML supported).
subjectYesEmail subject line.
from_emailNoSender email address. Falls back to AWS_SES_FROM_EMAIL env var.

Output Schema

NameRequiredDescriptionDefault
toYesRecipient email address
subjectYesEmail subject line
successYesWhether the email was sent successfully
timestampYesISO 8601 timestamp of when the email was sent
message_idYesAWS SES message ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls well short. It does not state that sending is irreversible and externally visible, what permissions or AWS credentials/region configuration are required, or what happens on delivery failure or partial recipient rejection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but its brevity comes at the cost of under-specification rather than efficiency. There is nothing structurally wrong, yet almost nothing is conveyed beyond the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an irreversible external-side-effect tool with six parameters and no annotations, so the description should do considerably more. The presence of an output schema excuses it from explaining return values, but the missing SES prerequisites and failure semantics leave real gaps.

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 description coverage is 100%, so all six parameters — including the from_email environment-variable fallback and HTML support in body — are already documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (send an email) plus the underlying transport (AWS SES), so an agent knows exactly what the tool does. There are no sibling tools to differentiate against, which is the only thing keeping this from a 5.

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?

There is no guidance on when to use this tool, no prerequisites, and no exclusions. An agent is not told that the sender identity must be verified in SES, that sandbox accounts can only send to verified recipients, or anything about expected volumes or alternatives.

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