Skip to main content
Glama
resend

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Webhook

create-webhook

Create a new webhook in Resend. A webhook allows you to receive notifications at a specified URL when certain events occur (e.g. email.sent, email.delivered, email.bounced, inbox.email.received).

Instructions

Create a new webhook in Resend. A webhook allows you to receive notifications at a specified URL when certain events occur (e.g. email.sent, email.delivered, email.bounced, inbox.email.received).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsYesArray of event types to subscribe to
endpointYesThe URL where webhook events will be sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.26.1
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "email.sent",
-  "email.scheduled",
-  "email.delivered",
-  "email.delivery_delayed",
-  "email.complained",
-  "email.bounced",
-  "email.opened",
-  "email.clicked",
-  "email.received",
-  "email.failed",
-  "email.suppressed",
-  "contact.created",
-  "contact.updated",
-  "contact.deleted",
-  "contact.topics.updated",
-  "domain.created",
-  "domain.updated",
-  "domain.deleted",
-  "suppression.added",
-  "suppression.removed",
-  "topic.created",
-  "topic.updated",
-  "topic.deleted"
-]New value: +[
+  "email.sent",
+  "email.scheduled",
+  "email.delivered",
+  "email.delivery_delayed",
+  "email.complained",
+  "email.bounced",
+  "email.opened",
+  "email.clicked",
+  "email.received",
+  "email.failed",
+  "email.suppressed",
+  "contact.created",
+  "contact.updated",
+  "contact.deleted",
+  "contact.topics.updated",
+  "domain.created",
+  "domain.updated",
+  "domain.deleted",
+  "suppression.added",
+  "suppression.removed",
+  "topic.created",
+  "topic.updated",
+  "topic.deleted",
+  "inbox.created",
+  "inbox.updated",
+  "inbox.deleted",
+  "inbox.thread.created",
+  "inbox.email.received",
+  "inbox.email.sent",
+  "inbox.thread.folder.updated",
+  "inbox.thread.assigned",
+  "inbox.thread.unassigned",
+  "inbox.thread.labels.updated",
+  "inbox.draft.created",
+  "inbox.draft.updated",
+  "inbox.draft.sent",
+  "inbox.draft.deleted"
+]
  2. Changed1 schema field changedv2.24.0
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "email.sent",
-  "email.scheduled",
-  "email.delivered",
-  "email.delivery_delayed",
-  "email.complained",
-  "email.bounced",
-  "email.opened",
-  "email.clicked",
-  "email.received",
-  "email.failed",
-  "email.suppressed",
-  "contact.created",
-  "contact.updated",
-  "contact.deleted",
-  "domain.created",
-  "domain.updated",
-  "domain.deleted",
-  "suppression.added",
-  "suppression.removed"
-]New value: +[
+  "email.sent",
+  "email.scheduled",
+  "email.delivered",
+  "email.delivery_delayed",
+  "email.complained",
+  "email.bounced",
+  "email.opened",
+  "email.clicked",
+  "email.received",
+  "email.failed",
+  "email.suppressed",
+  "contact.created",
+  "contact.updated",
+  "contact.deleted",
+  "contact.topics.updated",
+  "domain.created",
+  "domain.updated",
+  "domain.deleted",
+  "suppression.added",
+  "suppression.removed",
+  "topic.created",
+  "topic.updated",
+  "topic.deleted"
+]
  3. Changed1 schema field changedv2.18.0
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "email.sent",
-  "email.scheduled",
-  "email.delivered",
-  "email.delivery_delayed",
-  "email.complained",
-  "email.bounced",
-  "email.opened",
-  "email.clicked",
-  "email.received",
-  "email.failed",
-  "email.suppressed",
-  "contact.created",
-  "contact.updated",
-  "contact.deleted",
-  "domain.created",
-  "domain.updated",
-  "domain.deleted"
-]New value: +[
+  "email.sent",
+  "email.scheduled",
+  "email.delivered",
+  "email.delivery_delayed",
+  "email.complained",
+  "email.bounced",
+  "email.opened",
+  "email.clicked",
+  "email.received",
+  "email.failed",
+  "email.suppressed",
+  "contact.created",
+  "contact.updated",
+  "contact.deleted",
+  "domain.created",
+  "domain.updated",
+  "domain.deleted",
+  "suppression.added",
+  "suppression.removed"
+]
  4. Changed1 schema field changedv2.12.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. First observedv2.10.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys the concept of the resource but omits mutation traits an agent needs: whether creation returns a signing secret (relevant given the rotate-webhook-signing-secret sibling), permission/auth requirements, idempotency, or limits on number of webhooks/endpoints.

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?

Two tight sentences with the action front-loaded and no filler. The second sentence is explanatory rather than differentiating, but it does earn its place by grounding the term 'webhook' for an agent that may not know the product's event model.

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

Completeness3/5

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

For a simple two-parameter create tool with no output schema, the description covers the core purpose adequately. However, with zero annotation coverage it should say more about the write operation's side effects (e.g. secret issuance) and any preconditions, which leaves it only minimally complete.

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 both 'endpoint' and 'events' are already documented in the schema, setting the baseline at 3. The description reinforces the semantics with example event names (email.sent, email.bounced, inbox.email.received), but adds no format or validation detail 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?

States a specific verb and resource ('Create a new webhook in Resend') and the second sentence defines what a webhook is in this product, including example event types. The verb cleanly separates it from the list-/get-/update-/remove-webhook siblings without needing to name them.

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

Usage Guidelines2/5

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

The description explains what a webhook does but never says when to create one versus using an alternative, nor does it note prerequisites (e.g. needing a verified domain before subscribing to domain/email events, or that a signing secret is issued). Usage is only implied by the concept explanation.

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