Skip to main content
Glama

email_send

Adding a welcome, receipt, status, or alert email to an app? email_send sends one transactional email to one recipient on every plan. Without from, the platform-managed sender is used immediately; the project name appears as the sender label. from selects a verified sender domain of the app. Domains bought through us or connected with our nameservers are set up automatically; a domain hosted elsewhere is verified once in Settings → Domains. A caller cannot explicitly name a platform domain.

The platform-managed sender is transactional-only. A verified sender domain carries the branding of the app itself and its marketing email. Outbound transactional email is available on Free, Builder, Pro, Scale, and Enterprise. The plan's email allowance and send rate limit apply either way; current limits are at /v1/pricing. It takes html or text (or both). reply_to is optional.

Example:

{
  "project_id": "my-saas",
  "to": "alice@example.com",
  "subject": "Your order shipped",
  "html": "<p>Tracking number: ABC123</p>"
}

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email address
fromNoOptional sender on a verified sender domain. Omission selects the platform-managed transactional sender with the project name as its label.
htmlNoHTML body. Optional if text is set.
textNoPlaintext body. Optional if html is set.
subjectYesEmail subject line
reply_toNoOptional reply-to address.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the sender-selection rules, that a caller cannot name a platform domain, domain-verification prerequisites for externally hosted domains, plan availability across all tiers, and that allowance and rate limits apply with a pointer to /v1/pricing. These are exactly the behavioral facts an agent needs before attempting a send.

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 front-loaded with the bold use-case hook, then sender semantics, plan/limits, and an example – a sensible order. It is somewhat long and repeats html/text optionality already in the schema, but every paragraph carries usable information.

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?

For a 7-parameter write tool with no output schema and only minimal annotations, the description covers sender behavior, prerequisites, limits, and body requirements well. It never says what a successful send returns (e.g., a message id) or how failures surface, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns one more by adding a worked example payload and by explaining the consequence of omitting 'from' (platform-managed sender, project name as label) in operational terms. Most of the remaining parameter detail (html/text mutual optionality, reply_to) duplicates the schema.

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 lead sentence names a specific verb and resource ('sends one transactional email to one recipient') and scopes it to per-recipient transactional use on every plan, so an agent knows exactly what this does. It does not explicitly contrast with the sibling inbox_send or push_send, but the transactional-email framing is precise enough to route correctly.

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?

The bold opener ('Adding a welcome, receipt, status, or alert email to an app?') gives concrete use cases, and it explicitly separates transactional sending (platform sender, all plans) from branded/marketing sending (verified sender domain). What's missing is an explicit 'do not use this for X, use inbox_send instead' exclusion, so routing between siblings still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources