Mautic MCP Connector

mautic_create_company

Create a company record in Mautic by supplying a required company name. Omit confirm to preview the write before executing it.

Instructions

Create a company. POST /api/companies/new. companyname is required. 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": {
      "companyname": "<companyname>"
    },
    "name": "mautic_create_company"
  }
}

Input Schema

Name	Required	Description
`score`	No
`fields`	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.
`companyfax`	No
`companycity`	No
`companyname`	Yes
`companyemail`	No
`companyphone`	No
`companystate`	No
`companycountry`	No
`companywebsite`	No
`companyzipcode`	No
`companyaddress1`	No
`companyaddress2`	No
`companyindustry`	No
`companydescription`	No
`companyannual_revenue`	No
`companynumber_of_employees`	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 and idempotentHint=false, so the description gets credit for adding the non-obvious confirmation gate: the call only mutates when confirm is the boolean true, otherwise it previews. That is real behavioral value beyond the annotations, though it says nothing about duplicate-name handling or failure modes.

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 short sentences, each carrying a distinct fact (action, endpoint, required field, safety gate), with the action and the confirmation rule front-loaded. Nothing is wasted or repeated from structured fields unnecessarily.

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 an 18-parameter mutation with a nested object and no output schema, the definition covers the action and the safety gate but leaves the 'fields' bag and the response shape undocumented. Adequate to call correctly in the common case, not complete for power use.

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 only 6% across 18 parameters, so the description has to carry weight; it does explain the two most critical ones (companyname required, confirm as execute/dry-run switch). However, the opaque nested 'fields' object and 'score' are left unexplained, which is the main remaining risk.

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 company") plus the underlying endpoint, which cleanly separates it from mautic_update_company and mautic_get_company. It stops short of naming a sibling explicitly, so a 4 rather than a 5.

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?

Gives a concrete operational rule the agent must know: companyname is required and confirm must be omitted for a dry-run. It does not say when to prefer this over mautic_update_company (e.g., existing company vs. new), nor does it mention prerequisite permissions.

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

Deploy Server