Skip to main content
Glama
resend

Email Sending MCP

by resend

Manage Events

manage-events

Create, list, get, update, or remove event definitions to trigger automations. Events define named triggers your application sends to start workflows.

Instructions

Purpose: Create, list, get, update, or remove event definitions in Resend.

Events define named triggers that your application sends to start automations. Each event can have an optional schema that validates payload data.

Actions:

  • create: Define a new event with a name and optional schema.

  • list: List all event definitions (paginated).

  • get: Get event details by ID or name.

  • update: Update an event's schema.

  • remove: Delete an event. You MUST confirm with the user before removing.

Workflow: manage-events (create) → create-automation → send-event

Schema types: string, number, boolean, date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoEvent name (for create). Use dot notation like "user.created". Cannot start with "resend:".
afterNoCursor for forward pagination (for list).
limitNoNumber of events to retrieve (for list). Default: 20.
actionYesThe operation to perform.
beforeNoCursor for backward pagination (for list).
schemaNoEvent payload schema (for create, update). Maps field names to types. Pass null to remove the schema.
identifierNoEvent ID or name (for get, update, remove).
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that remove is destructive and requires confirmation, and explains schema role and naming conventions. It lacks mention of idempotency or error handling but is sufficient for a CRUD tool.

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?

The description is well-structured with clear sections, front-loaded key information, and no extraneous text. Every sentence contributes useful context.

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?

Given the 7 parameters and no annotations or output schema, the description covers all necessary aspects: purpose, actions, workflow, schema types, and confirmation for deletion. It is self-contained and comprehensive.

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%, baseline 3. The description adds value beyond schema by explaining dot notation for name, schema type mapping, and the effect of null schema. It also clarifies pagination cursors and identifier usage.

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 the tool manages event definitions in Resend with specific verbs (create, list, get, update, remove). It distinguishes itself from sibling tools as the only one for event definition management.

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 provides a workflow hint (manage-events → create-automation → send-event) and warns that removal requires user confirmation. It does not explicitly state when not to use, but the context makes it clear this is the dedicated management tool.

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