Mautic MCP Connector

mautic_list_segments

Read-only

List Mautic segments with pagination, search, and ordering to find and manage audience groups. Retrieve segment records through the Mautic REST API using offset and limit controls.

Instructions

List segments. GET /api/segments. The collection key in the Mautic body is lists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mautic_list_segments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size. Defaults to 30. Capped by MAUTIC_MAX_LIMIT.
`start`	No	Row offset. Defaults to 0.
`search`	No	Mautic search string or search command.
`minimal`	No
`orderBy`	No
`orderByDir`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine value by naming the response collection key ('lists') in the Mautic body, which matters because there is no output schema and the key differs from the tool name. It says nothing about pagination behavior, rate limits, or auth requirements, so it stays at a moderate level.

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 terse sentences with the primary action front-loaded and no filler. Nothing is wasted, though the terseness borders on under-specification rather than tight editing.

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?

With no output schema, the description carries responsibility for describing the return shape; it reveals only the envelope key ('lists') and not the per-segment fields or pagination metadata. For a six-parameter listing tool with no annotations covering params, an agent is left guessing about the undocumented query options.

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?

Schema coverage is only 50%: limit, start and search are documented in the schema, but minimal, orderBy and orderByDir have no descriptions at all. The description text does not mention any parameter, so it fails to compensate for the gap — particularly for 'minimal', which is an opaque Mautic-specific flag an agent cannot guess.

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 and resource ('List segments') and pins the underlying endpoint (GET /api/segments), so the operation is unambiguous. It does not distinguish itself from segment-adjacent siblings such as mautic_add_contact_to_segment or the broader list_* family, but the name plus verb makes the read-only listing intent clear.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the tool name alone that this is the entry point for discovering segments before calling mautic_add_contact_to_segment or mautic_send_email_to_segment.

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

Deploy Server