Mautic MCP Connector

mautic_create_note

Create a note on a Mautic contact with text and an optional type such as general, email, call, or meeting. Omit confirm to preview the write as a dry run before saving.

Instructions

Create a note. POST /api/notes/new with lead, text, and optional type (general, email, call, meeting). Omit confirm for a dry-run preview.

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": {
      "lead": "<lead>",
      "text": "<text>"
    },
    "name": "mautic_create_note"
  }
}

Input Schema

Name	Required	Description
`lead`	Yes	Contact ID for the note.
`text`	Yes
`type`	No
`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.
`dateTime`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is carried structurally. The description adds real behavior: that omitting confirm yields a non-mutating preview rather than an error, which is the key operational trait for a write tool and is not inferable from the hints alone.

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 compact sentences, front-loaded with the action and followed by the concrete invocation details. The raw endpoint path is the only marginally low-value element, but it is short and helps an agent confirm target semantics.

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 five-parameter mutation tool with one undocumented field (dateTime) and no output schema, the description covers the essentials: what is written, required fields, optional type values, and the dry-run gate. Missing detail about what a preview returns or any permission requirements keeps it short of fully complete.

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?

With only 40% schema description coverage, the description carries weight, and it does clarify lead, text, and the type enum values (general, email, call, meeting). However, it restates what the enum already declares and says nothing about dateTime or the constraints on text, so it only partially compensates for the coverage gap.

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?

"Create a note" states a specific verb and resource, and the endpoint (POST /api/notes/new) plus the required lead/text fields confirm exactly what is being written. It implicitly distinguishes itself from the listing sibling mautic_list_notes, but never names alternatives explicitly.

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 dry-run hint ("Omit confirm for a dry-run preview") gives useful call-time guidance for how to invoke safely, but there is no statement of when to choose this tool over siblings such as mautic_get_contact_activity or when note creation is appropriate.

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

Deploy Server