Skip to main content
Glama
Sign In
@kieksme/listmonk-mcp

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Unsaved Template

listmonk_preview_template_draft
Read-onlyIdempotent

Render an HTML preview of an unsaved Listmonk template body and type without saving or modifying data, so you can check formatting before creating a template.

Instructions

Renders an HTML preview of an UNSAVED template body/type combination, without creating or modifying anything. Use before listmonk_create_template to check formatting.

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": {
      "template_type": "<template_type>",
      "body": "<body>"
    },
    "name": "listmonk_preview_template_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesUnsaved HTML body to render a preview of.
template_typeYesTemplate type, e.g. 'campaign', 'campaign_visual', or 'tx'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), but the description adds the meaningful distinction that the input is unsaved draft content and restates that nothing is created or modified. Naming the return as an HTML preview is useful since there is no output schema; pagination/size limits or error behavior for malformed bodies are not mentioned.

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?

Two sentences, front-loaded with the core action and its non-mutating guarantee, then the recommended placement in the workflow. Nothing is wasted.

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?

For a two-parameter, no-output-schema tool, the description covers what it produces (HTML preview), what it does not do (no create/modify), and where it fits in the flow. Only minor gaps remain, such as what happens on invalid template_type or how the preview is returned.

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% with descriptions on both body and template_type, so the schema already carries the detail. The description adds only the notion that body/type are an unsaved draft pair, not new syntax or format guidance. Baseline 3 is appropriate.

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?

The description gives a specific verb and resource ('Renders an HTML preview of an UNSAVED template body/type combination') and capitalizes UNSAVED, which cleanly separates it from the sibling listmonk_preview_template that presumably renders a stored template.

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

Usage Guidelines4/5

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

It states the sequencing explicitly: 'Use before listmonk_create_template to check formatting.' That is concrete when-to-use guidance, though it never names the alternative to use when the template already exists (listmonk_preview_template) and gives no explicit exclusion case.

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