Skip to main content
Glama
Sign In

Mailercloud

by com.mailercloud.mcp
OverviewDiscussionsAdmin

update_webhook

DestructiveIdempotent

Update an existing webhook's configuration. Only the fields given (name, url, events) are changed: the tool reads the webhook first and resends its current values for the rest, since the API needs all three. events replaces the current set. Use toggle_webhook to enable or disable. Set dry_run: true to see the merged values that would be sent.

Input Schema

NameRequiredDescriptionDefault
urlNoNew webhook URL (HTTPS, public host)
nameNoNew webhook name
eventsNoEvents to subscribe to (replaces the current set)
dry_runNoValidate and show what would change without changing anything
webhook_idYesWebhook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / events / items / enum
      Added value: +[
+  "campaign_sent",
+  "campaign_opened",
+  "campaign_clicked",
+  "unsubscribe",
+  "campaign_error",
+  "spam",
+  "hard_bounce"
+]
    • changedInput schema / properties / webhook_id / description
      Previous value: -"Webhook ID,required"New value: +"Webhook ID"
  2. Changed7 schema fields changed
    • removedInput schema / properties / api_key
      Removed value: -{
-  "description": "MailerCloud API key",
-  "type": "string"
-}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Validate and show what would change without changing anything",
+  "type": "boolean"
+}
    • addedInput schema / properties / events
      Added value: +{
+  "description": "Events to subscribe to (replaces the current set)",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • removedInput schema / properties / fields
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Fields to update,required",
-  "type": "object"
-}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "New webhook name",
+  "type": "string"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "New webhook URL (HTTPS, public host)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "webhook_id",
-  "fields"
-]New value: +[
+  "webhook_id"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses the non-obvious read-modify-write implementation (reads the webhook, resends current values for unchanged fields because the API requires all three), which explains why a partial update behaves atomically. Also explains that events replaces rather than appends — consistent with destructiveHint=true — and that dry_run returns merged values rather than a boolean.

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?

Four compact sentences, front-loaded with the mutation scope, then semantics, then alternative-tool routing, then the preview affordance. No repeated or decorative content.

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?

For a 5-parameter mutation tool with a destructive annotation and no output schema, everything an agent needs is present: what changes, what is preserved, replacement vs. additive semantics, how to preview safely, and which sibling to use instead. Nothing material is left to inference.

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%, so parameter definitions are already documented; the description still adds real meaning by clarifying that omitted fields are preserved via internal resend and that events is a replacement set, not an addition. dry_run's return content (merged values) is also clarified beyond the schema's generic "show what would change".

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 ("Update an existing webhook's configuration") and immediately scopes what is mutable (name, url, events). It is easily separable from create_webhook, delete_webhook, get_webhook, and toggle_webhook in the sibling list.

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 routes the enable/disable case to toggle_webhook and offers dry_run: true as a preview path before committing. The implicit exclusion (only existing webhooks, only these three fields) is also stated, so there is no ambiguity about when this tool applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mailercloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources