Skip to main content
Glama
resend

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update Webhook

update-webhook

Update an existing webhook in Resend. You can change the endpoint URL, subscribed events, or enable/disable the webhook.

Instructions

Update an existing webhook in Resend. You can change the endpoint URL, subscribed events, or enable/disable the webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNoNew array of event types to subscribe to
statusNoWebhook status
endpointNoNew URL where webhook events will be sent
webhookIdYesWebhook ID

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 exist, so the description carries the full behavioral burden, and it mostly restates the schema's editable properties. It does not disclose whether the events array replaces or merges with existing subscriptions, what permissions are needed, whether changes are reversible, or what happens to in-flight deliveries — all material for a mutation tool.

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 short sentences with the action front-loaded and no filler. The only mild waste is the brand qualifier 'in Resend', which adds nothing for an agent already operating in that namespace.

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 4-parameter mutation tool with no annotations and no output schema, the description identifies the mutable surface but omits replacement semantics, permission requirements, and side effects. It is adequate to invoke the tool but not to predict its consequences.

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 baseline is 3. The description names the three optional fields at a high level but adds no format, constraint, or replacement semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update an existing webhook in Resend') and enumerates the mutable fields (endpoint URL, subscribed events, enable/disable). It implicitly separates itself from create-webhook/remove-webhook by saying 'existing', but never names a sibling explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'existing' and by the CRUD naming convention in the sibling set. There is no statement of when to prefer this over create-webhook or remove-webhook, no prerequisites, and no guidance on partial vs full updates.

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