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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Unsaved Campaign Content

listmonk_preview_campaign_draft
Read-onlyIdempotent

Renders an HTML or text preview for an unsaved campaign body using the campaign’s saved subject and lists, without saving changes. Use it to check formatting before updating a campaign.

Instructions

Renders an HTML/text preview of an UNSAVED body/content_type combination for campaign id, using the campaign's other saved fields (subject, lists), without persisting anything. Use before listmonk_update_campaign 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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "listmonk_preview_campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign to render the preview for (its lists/subject/etc are used, body is overridden).
bodyYesUnsaved HTML/markdown body to render a preview of.
template_idNo
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'without persisting anything' largely restates structured data. The description does add real context beyond annotations: the campaign's saved fields (subject, lists) are reused while body is overridden, which tells the agent the campaign must already exist and that context comes from stored state. No mention of permissions or output shape.

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, no filler. The core behavior and its non-persisting nature come first, and the workflow hint ('use before listmonk_update_campaign') is placed last, which is the right information order.

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 and four parameters, the description does most of the necessary work: it says what is rendered (HTML/text), what is overridden (body), and what is preserved (saved subject/lists). The remaining gaps are small but real – template_id is never explained, and it does not say how HTML vs text output is selected.

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 50%: id and body are documented in the schema, content_type is self-explanatory via its enum, but template_id has no description anywhere. The description's phrase 'body/content_type combination' ties two parameters together usefully, yet it leaves template_id unexplained, which is the one genuinely ambiguous input.

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 (renders a preview) and resource (campaign body/content_type) and, crucially, the scope qualifier 'UNSAVED' plus 'without persisting anything'. That qualifier is what separates it from sibling preview tools like listmonk_get_campaign_preview and listmonk_preview_campaign_text, so an agent can route correctly without opening schemas.

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?

Gives an explicit use case with a named sibling: 'Use before listmonk_update_campaign to check formatting.' That is concrete when-to-use guidance. It does not state when NOT to use it or contrast it with the other campaign/template preview siblings, so it stops short of a 5.

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