Skip to main content
Glama
Mautic MCP Connector

Mautic MCP Connector

by si-essence

mautic_add_contact_to_company

Idempotent

Add a contact to a company in Mautic, with an optional dry-run preview before executing the write.

Instructions

Add a contact to a company. POST /api/companies/{companyId}/contact/{contactId}/add. 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": {
      "company_id": "<company_id>",
      "contact_id": "<contact_id>"
    },
    "name": "mautic_add_contact_to_company"
  }
}

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.
company_idYes
contact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds the two-step dry-run/confirm model, which is genuine behavioral context, but that same mechanic is spelled out in more detail in the confirm parameter's schema description. Nothing is said about permissions, side effects on the company record, or what happens when the contact is already a member.

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 with the purpose front-loaded and no filler. The raw endpoint path 'POST /api/companies/{companyId}/contact/{contactId}/add' is arguably redundant given the parameter names, but it is compact and the rest is tight.

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 three-parameter write tool with no output schema, the description covers the action and the dry-run gate but leaves gaps: no mention of idempotent no-op behavior when the contact is already linked, no error conditions, and no return shape. It is adequate but not complete.

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

Parameters2/5

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

Only confirm (33% coverage) is documented in the schema, and the description merely restates the dry-run behavior already covered there. The two required identifiers, company_id and contact_id, get no explanation at all in either the description or the schema, so the description fails to compensate for the low coverage.

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?

The description opens with a specific verb+resource ('Add a contact to a company'), which is unambiguous and clearly distinct from siblings like mautic_add_contact_to_campaign or mautic_add_contact_to_segment. It does not explicitly name the inverse sibling mautic_remove_contact_from_company, so it falls just short of full differentiation.

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 sentence 'Omit confirm for a dry-run preview' gives operational guidance on how to invoke it safely, which is useful. However, there is no statement of when to use this tool versus alternatives (e.g. when a contact should be attached to a company vs a segment), and no prerequisites are given beyond the confirm flag.

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