Mautic MCP Connector

mautic_list_emails

Read-only

List and page through Mautic emails using search, ordering, and offset controls to locate marketing or campaign email records.

Instructions

List emails. GET /api/emails.

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_emails"
  }
}

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

C2.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond the endpoint path: no note on pagination behavior, default result size, search-string syntax, or whether the list is workspace-scoped or global (a real concern given openWorldHint).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and free of padding, so structure is fine. However, the second fragment simply repeats the HTTP route, which is arguably the least useful thing to spend the one available sentence on, and the result is under-specification rather than true conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter listing tool with no output schema and half the parameters undocumented, the description should at least explain filtering/search and pagination semantics and what an email record contains. It supplies none of that, leaving the agent to guess how results are shaped and bounded.

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 and start are documented in the schema, but minimal, orderBy and orderByDir have no description at all, and the description compensates for none of them. With low coverage, the description was expected to carry meaning for at least the sorting and minimal-shape parameters, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List emails" essentially restates the tool name mautic_list_emails, with "GET /api/emails" adding only the underlying REST path. Nothing distinguishes it from siblings such as mautic_get_email (single email), mautic_get_email_stats, or the send-email tools, so an agent must infer the difference from names alone.

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 guidance on when to use this listing endpoint versus mautic_get_email or mautic_get_email_stats, and no mention of prerequisites or typical contexts. Usage is only implied by the verb "List".

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

Deploy Server