Mautic MCP Connector

mautic_create_webhook

Create a Mautic webhook with a name, URL, and triggers, with optional dry-run preview and trigger validation before saving.

Instructions

Create a webhook. POST /api/hooks/new with name, webhookUrl, and triggers. Optional description, eventsOrderbyDir (ASC or DESC), and isPublished. When confirm is true, trigger names are checked against GET /api/hooks/triggers before the create. Omit confirm for a dry-run preview that does not call Mautic. 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": {
      "name": "<name>",
      "webhookUrl": "<webhookUrl>",
      "triggers": "<triggers>"
    },
    "name": "mautic_create_webhook"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`confirm`	No	Set to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
`triggers`	Yes
`webhookUrl`	Yes
`description`	No
`isPublished`	No
`eventsOrderbyDir`	No	ASC or DESC. Lowercase asc and desc are accepted and sent in uppercase.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the dry-run/confirm gate, the pre-flight trigger validation call, and that the response secret is stripped. These are non-obvious behaviors an agent could not infer from readOnlyHint=false and destructiveHint=false.

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 dense sentences, front-loaded with the action and endpoint, then the confirm/dry-run behavior, then the response note. No filler or repetition.

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?

For a mutation tool with no output schema, it covers the write path, the safety gate, and one return-value detail (secret removed). It could say more about what the created webhook object contains, but nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 29% schema description coverage, the description compensates by covering all seven parameters: name, webhookUrl, triggers, optional description, eventsOrderbyDir (ASC/DESC), isPublished, and the confirm flag. It adds meaning the schema alone does not convey, particularly the confirm semantics.

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 ('Create a webhook') and names the endpoint plus the three required fields, so the agent knows exactly what is produced. It does not explicitly contrast itself with siblings like mautic_list_webhooks or mautic_get_webhook, but the create verb is unambiguous against those read tools.

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

Usage Guidelines4/5

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

Gives concrete operational guidance: set confirm=true to execute, omit confirm for a dry-run preview that does not call Mautic, and trigger names are validated against GET /api/hooks/triggers when confirming. It stops short of naming alternative tools or stating when not to create a webhook.

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

Deploy Server