Skip to main content
Glama
resend

Email Sending MCP

by resend

Send Broadcast

send-broadcast

Send or schedule a broadcast email by providing the broadcast ID. Use after creating a broadcast to deliver it to your audience.

Instructions

Purpose: Send (or schedule) an existing broadcast by ID. The broadcast must have been created with create-broadcast first.

NOT for: Sending a new one-off email (use send-email). Not for creating the broadcast content (use create-broadcast).

Returns: Send confirmation and broadcast ID.

When to use:

  • User has created a broadcast and says "send it", "go ahead and send", "schedule this for tomorrow"

  • After create-broadcast; call send-broadcast with the returned ID to deliver to the audience

  • Optional scheduledAt: natural language or ISO 8601 for scheduled send

Workflow: create-broadcast → send-broadcast. Use list-broadcasts to find existing draft/sent broadcasts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
broadcastIdYesBroadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
scheduledAtNoWhen to send the broadcast. Value may be in ISO 8601 format (e.g., 2024-08-05T11:52:01.858Z) or in natural language (e.g., "tomorrow at 10am", "in 2 hours", "next day at 9am PST", "Friday at 3pm ET"). If not provided, the broadcast will be sent immediately.
Behavior4/5

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

Describes the action (send/schedule), return value (confirmation and ID), and workflow. No annotations provided, so description carries the burden. Does not discuss edge cases or rate limits, but is sufficient for basic use.

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?

Well-structured with bold headings and bullet points. Front-loaded purpose, no fluff. Every sentence earns its place.

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

Completeness5/5

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

Covers purpose, usage guidelines, parameter details, workflow, and return info. Sufficient for correct agent invocation given tool simplicity and no output schema.

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?

Input schema covers parameters with 100% coverage. Description adds meaning: broadcastId can be a URL, scheduledAt accepts natural language. Adds value beyond 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?

Clearly states the tool sends or schedules an existing broadcast by ID, and distinguishes from create-broadcast and send-email. Specific verb+resource+scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (after create-broadcast) and when not (for one-off emails or creating content). Names alternative tools (send-email, create-broadcast).

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

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