Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_webhook

DestructiveIdempotent

Delete a webhook to immediately stop event notifications to its URL. This action is irreversible and requires list and webhook IDs.

Instructions

Delete a webhook, immediately stopping event notifications to its URL.

Irreversible. Do not use when you want to temporarily pause notifications; webhooks have no pause mechanism. Use create_webhook to set up a replacement afterward.

Returns 404 error if webhook_id or list_id is invalid.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. webhook_id: The webhook ID to delete. Obtain from list_webhooks.

Returns: JSON with status ("deleted"), webhook_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
list_idYes
webhook_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds context: 'Irreversible' and error case 'Returns 404 error if webhook_id or list_id is invalid.' This adds value beyond annotations, though idempotency is not directly discussed.

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?

Description is concise with a clear structure: main action, usage note, error case, then args and returns. It avoids unnecessary words, though the args section somewhat duplicates schema.

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

Completeness4/5

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

Given output schema exists, return value details are covered. Description covers purpose, usage guidelines, behavior, and param explanations (except account). It is quite complete for a delete operation, but missing account param discussion prevents a 5.

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 coverage is 0%, so description must compensate. It explains list_id (format and source) and webhook_id (source). However, the optional 'account' parameter is mentioned in schema but not explained in description, leaving a gap.

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 'Delete a webhook, immediately stopping event notifications to its URL.' This is a specific verb and resource, and it distinguishes from siblings by noting that it's not for pausing and that a new webhook can be created afterward.

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 says 'Do not use when you want to temporarily pause notifications' and suggests 'Use create_webhook to set up a replacement afterward.' This provides clear when-to-use and when-not-to-use guidance with alternative.

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