Skip to main content
Glama
helbertparanhos

resend-email-mcp

preview_email

Read-onlyIdempotent

Validate and preview an email message without sending it. Resolves sender, checks payload, reads local attachments, and returns summary with warnings.

Instructions

Dry-run an email WITHOUT sending it. Resolves the final from (incl. RESEND_FROM default), validates the payload, reads/sizes any local attachments, and returns a summary plus warnings. Use to verify a message before calling send_email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoSender, e.g. "Acme <hello@acme.com>". Falls back to RESEND_FROM. Domain must be verified.
toYesRecipient address(es), e.g. "user@example.com" or ["a@x.com","b@y.com"]
subjectYesEmail subject line
htmlNoHTML body (provide html and/or text)
textNoPlain-text body (provide html and/or text)
ccNoRecipient address(es), e.g. "user@example.com" or ["a@x.com","b@y.com"]
bccNoRecipient address(es), e.g. "user@example.com" or ["a@x.com","b@y.com"]
replyToNoReply-To address(es). Falls back to RESEND_REPLY_TO.
scheduledAtNoSchedule for later: ISO-8601 or natural language like "in 1 hour" / "tomorrow at 9am"
attachmentsNo
tagsNo
headersNoCustom headers, e.g. {"X-Entity-Ref-ID": "123"}
templateIdNoSend using a saved template instead of html/text
templateDataNoVariables to interpolate into the template
idempotencyKeyNoOptional Idempotency-Key to make retries safe (avoids duplicate sends)
Behavior5/5

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

Annotations (readOnlyHint, destructiveHint, etc.) align with the description. The description adds valuable behavioral details: resolving the from field, validating the payload, reading/sizing local attachments, and returning a summary plus warnings. No contradictions.

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?

Two sentences with no wasted words. The first sentence immediately states the core purpose. Information is front-loaded and easy to parse.

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 15 parameters, nested objects, and no output schema, the description covers the core behavior adequately ('returns a summary plus warnings'). However, it omits details about what the summary contains or the structure of warnings, which would improve completeness.

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 description coverage is 87%, so parameters are well-documented in the schema. The description adds value by explaining the 'from' fallback (RESEND_FROM default) and local attachment handling beyond what the schema provides.

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 'Dry-run an email WITHOUT sending it', using a specific verb and resource. It distinguishes itself from the sibling 'send_email' by explicitly noting it doesn't send. The title 'Preview Email' aligns well.

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 description explicitly advises 'Use to verify a message before calling send_email', providing clear context for when to use this tool. While it doesn't list explicit alternatives or exclusions, the context is sufficient for an agent to differentiate.

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/helbertparanhos/resend-email-mcp'

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