@kieksme/listmonk-mcp

Create Template

listmonk_create_template

Creates new Listmonk campaign, visual email, or transactional templates from a template name and HTML body, with subject line support for transactional messages.

Instructions

Creates a new campaign or transactional template.

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": {
      "name": "<name>",
      "type": "<type>",
      "body": "<body>"
    },
    "name": "listmonk_create_template"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	HTML body of the template.
`name`	Yes
`type`	Yes
`subject`	No	Subject line (only used when type is 'tx').
`body_source`	No	JSON source for the visual email builder (only for 'campaign_visual').
`response_format`	No	Output format: 'markdown' for human-readable text (default) or 'json' for machine-readable data.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 4, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare non-readonly, non-idempotent, non-destructive, and open-world behavior, so the description's burden is lower, but it adds nothing beyond them. It does not mention that repeated calls create duplicates, whether names must be unique, or that the type choice gates which other parameters matter.

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?

One short, front-loaded sentence with no wasted words, but the brevity reflects under-specification rather than efficiency. It leaves no room for the conditional-parameter guidance this tool needs.

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 non-idempotent create operation with six parameters, mutually exclusive modes, and no output schema, the description is far too thin. It should at minimum cover the template type semantics and the conditional requirements of subject and body_source.

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 67%, leaving real gaps: the description never explains the campaign vs campaign_visual vs tx distinction or that 'subject' is only meaningful for tx and 'body_source' only for campaign_visual. The phrase 'campaign or transactional template' gestures at the enum but omits the visual-builder variant entirely.

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 pairs a specific verb ('Creates') with a specific resource ('new campaign or transactional template'), which tells an agent more than the name alone. It does not, however, distinguish this from sibling write operations such as listmonk_update_template or listmonk_create_campaign.

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 versus listmonk_update_template, listmonk_preview_template, or listmonk_create_campaign. The only implied guidance is that the tool targets templates rather than campaigns, which an agent could infer from the name.

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

Deploy Server