Skip to main content
Glama
tecspda

listmonk-mcp-ts

by tecspda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_template

Create a campaign layout or transactional email template and return its ID for use in other Listmonk operations.

Instructions

Create a template and return its ID. Type 'campaign' is a layout that wraps campaign bodies; type 'tx' is a transactional email template that needs a subject and is sent with send_transactional_email. For large HTML bodies prefer create_template_from_file.

Input Schema

NameRequiredDescriptionDefault
bodyYesFull template HTML. A 'campaign' template must contain {{ template "content" . }} where the campaign body goes
nameYesTemplate name
typeNoTemplate type: 'campaign' or 'tx' (transactional)campaign
subjectNoSubject line (required for 'tx' transactional templates)
is_defaultNoWhether this is default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / body / description
      Previous value: -"Template HTML body"New value: +"Full template HTML. A 'campaign' template must contain {{ template \"content\" . }} where the campaign body goes"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/safety profile is covered. The description adds two useful facts, that the new template's ID is returned and that 'tx' templates require a subject, but it does not warn about non-idempotent duplicate creation (e.g. whether name must be unique or what happens on repeat calls).

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action and return value, then type semantics, then the sibling alternative. Every sentence carries information an agent needs, with no filler.

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

Completeness4/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 compensates by stating that the ID is returned, and it covers both template types and the large-body alternative. It stops short of addressing naming/uniqueness behavior or validation failures, which would matter for a non-idempotent create.

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

Parameters3/5

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

Schema coverage is 100%, so the body placeholder requirement, the type default and the subject requirement are already documented in the schema. The description reinforces the type/subject relationship and the meaning of 'campaign' vs 'tx', but adds no formatting or constraint detail beyond that. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Create a template") and immediately names the return value ("return its ID"). It also distinguishes this tool from its sibling create_template_from_file, so an agent can pick correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use create_template_from_file for large HTML bodies, and 'tx' templates are sent with send_transactional_email. This names alternatives and the conditions that select them, which is exactly the routing help missing from most definitions.

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