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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Saved Template

listmonk_preview_template
Read-onlyIdempotent

Render an HTML preview of a saved Listmonk template by ID exactly as stored, so you can verify its current content before editing or sending.

Instructions

Renders an HTML preview of an existing saved template by id, exactly as currently stored.

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": {
      "id": "<id>"
    },
    "name": "listmonk_preview_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe saved template to render.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds two useful facts the annotations do not: the output is rendered HTML, and no unsaved/draft state is applied. It says nothing about rendering errors, missing-template behavior, or payload size, so it clears the lowered bar but not generously.

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?

One sentence, front-loaded with the verb and output format, with no filler. The qualifier 'exactly as currently stored' is the only extra clause and it carries real semantic weight.

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 single-parameter read tool with full annotation coverage and no output schema, the definition covers purpose, subject, and the stored-vs-draft distinction adequately. The remaining gap is routing guidance among the template-preview and template-get siblings, which would make it complete.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that it is the saved template to render. The description only reinforces 'by id' and adds that the id refers to an existing saved template rather than a draft, which is marginal added meaning.

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 (renders), a specific output (an HTML preview), and a specific resource (an existing saved template keyed by id). The phrase 'exactly as currently stored' implicitly distinguishes it from the sibling listmonk_preview_template_draft, but it never names that sibling, so the differentiation requires inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer you call this when you want to see how a stored template looks. There is no explicit statement of when to prefer this over listmonk_get_template (raw source) or listmonk_preview_template_draft (unsaved changes), and no preconditions are given.

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