Skip to main content
Glama
Sign In
Mautic MCP Connector

Mautic MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mautic_delete_webhook

DestructiveIdempotent

Delete a Mautic webhook by ID; omit confirmation for a dry-run preview, then confirm to remove the webhook and its secret.

Instructions

Delete a webhook. DELETE /api/hooks/{id}/delete. Omit confirm for a dry-run preview. The response secret is removed.

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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "mautic_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: a non-destructive dry-run path when confirm is omitted, and the note that "the response secret is removed", which warns that the returned payload will not include the webhook secret.

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?

Three short sentences, front-loaded with the action, then the endpoint, then the dry-run caveat. The endpoint fragment is largely redundant with the tool name but is the only slightly wasteful element.

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 destructive, open-world mutation with no output schema, the description should say what a successful call or a dry-run preview actually returns (deleted object, confirmation message, affected triggers). It covers the key safety lever but leaves the response shape and side effects on related webhook triggers unstated.

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 50%: confirm is documented in the schema, while webhook_id has no description at all. The description reinforces the dry-run meaning of confirm but says nothing about the accepted id forms (integer or numeric string) that the schema's anyOf leaves implicit.

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?

"Delete a webhook" states a specific verb and resource, and the deletion action cleanly separates it from the webhook siblings (mautic_create_webhook, mautic_get_webhook, mautic_list_webhooks). The endpoint line reinforces exactly which API operation is performed.

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?

The description explains the dry-run mode ("Omit confirm for a dry-run preview"), which is invocation guidance for the parameter rather than tool-selection guidance. It never says when deletion is appropriate versus updating or leaving the webhook in place, so usage is only implied by the verb.

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