Skip to main content
Glama
Sign In
Mautic MCP Connector

Mautic MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mautic_list_form_submissions

Read-only

Lists submissions for a specified Mautic form, with pagination, search, ordering, and optional minimal output so users can review form responses.

Instructions

List submissions for a form. GET /api/forms/{formId}/submissions.

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": {
      "form_id": "<form_id>"
    },
    "name": "mautic_list_form_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Defaults to 30. Capped by MAUTIC_MAX_LIMIT.
startNoRow offset. Defaults to 0.
searchNoMautic search string or search command.
form_idYes
minimalNo
orderByNo
orderByDirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 elsewhere. Beyond repeating the HTTP verb/path, the description says nothing about pagination behavior, the MAUTIC_MAX_LIMIT cap or the shape of results — all things an agent would need. It adds almost no behavior beyond the structured fields.

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 short sentences, front-loaded, with zero filler. The endpoint path is mildly redundant with the tool name but does confirm the resource hierarchy. It is not underspecified out of brevity alone — it simply carries no guidance.

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 7-parameter listing tool with no output schema and 43% parameter description coverage, the description is far too thin. It never says what a submission record contains, whether results are paginated, or how search/minimal/orderBy affect the output, leaving the agent to guess at call correctness.

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 43% across 7 parameters, so the description carries a real compensation burden and provides none: form_id, minimal, orderBy and orderByDir are undocumented in both places. The limit/start/search descriptions live entirely in the schema, not in the description, so no meaning is added.

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 ('List submissions for a form') and pins the exact REST endpoint, so the agent knows it retrieves form submission records rather than form definitions (mautic_list_forms / mautic_get_form). It stops short of explicitly naming those siblings, so it doesn't fully earn 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternatives named. Usage is only implied by the required form_id, and nothing tells the agent how this differs from mautic_get_form or mautic_get_stats when hunting for submission data.

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

Deploy Server

Other Tools