Skip to main content
Glama
Sign In
Email Sending MCP

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Inbox

create-inbox

Create a Resend inbox to receive email at a verified domain address and group messages into threads; enable forwarding to route mail from your current provider.

Instructions

Create an inbox in Resend. An inbox receives email at an address on one of your domains and groups what arrives into threads. The domain must already be verified for receiving, or set forwarding to true, and Resend returns a receiving address you point your existing mail provider at instead. A team at the inbox limit of its plan gets a 403, and a blocked account gets a 451.

Input Schema

NameRequiredDescriptionDefault
nameNoInternal name for the inbox, shown in the Resend dashboard. Max 64 characters.
fromNameNoDisplay name shown on mail this inbox sends or replies to (the name in "Name <address>"). Max 78 characters. It cannot contain a colon, <, >, or line breaks.
forwardingNoReceive mail by forwarding instead of by MX record. Resend returns a receiving address to point your existing mail provider at. Use this when the domain sends through Resend but still receives mail elsewhere. Default: false
emailAddressYesEmail address the inbox receives at (e.g. "support@example.com"). The domain must already exist in Resend. The part before the @ is at most 64 characters and contains only letters, numbers, and . _ % -, so a + is rejected. It cannot start or end with a dot or contain two dots in a row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.27.1
    • changedInput schema / properties / emailAddress / description
      Previous value: -"Email address the inbox receives at (e.g. \"support@example.com\"). The domain must already exist in Resend."New value: +"Email address the inbox receives at (e.g. \"support@example.com\"). The domain must already exist in Resend. The part before the @ is at most 64 characters and contains only letters, numbers, and . _ % -, so a + is rejected. It cannot start or end with a dot or contain two dots in a row."
  2. Addedv2.26.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world write. The description adds meaningful context beyond that: domain verification prerequisite, the forwarding mode that returns a receiving address to point an external mail provider at, plus 403 for plan-limit teams and 451 for blocked accounts. It does not describe the success response shape, but error and prerequisite disclosure is solid.

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?

Three sentences, front-loaded with the action and definition, then prerequisites/errors. Slightly dense but every sentence carries information. 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?

For a creation tool with no output schema and full schema coverage, the description covers the key prerequisites, the forwarding variant, and failure modes. The main gap is the success return value, which matters for an agent that needs the new inbox ID, but the core decision inputs are present.

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 the schema already documents name, fromName, forwarding, and emailAddress in detail. The description restates some of that (forwarding behavior, domain must exist) but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Create an inbox in Resend') and then defines what an inbox actually does (receives mail at a domain address, groups into threads). This clearly distinguishes it from get-inbox, update-inbox, list-inboxes, and remove-inbox.

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?

Gives the precondition for use: the domain must already be verified for receiving, or forwarding must be true. It also explains the forwarding alternative's purpose (domain sends through Resend but receives elsewhere). It does not explicitly contrast with create-domain or other setup tools, so it stops short of a 5.

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