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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Campaign Preview

listmonk_get_campaign_preview
Read-onlyIdempotent

Renders an HTML or plain-text preview of a saved Listmonk campaign so you can verify exactly how it will appear before sending.

Instructions

Renders an HTML (or plain-text) preview of a campaign exactly as currently saved in Listmonk.

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_get_campaign_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/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 that the render reflects the persisted state rather than edits, which is useful. It does not say what is returned (rendered markup string? URL?) or how the '(or plain-text)' alternative is selected, given there is no format parameter.

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, no filler, with the key scoping qualifier ('currently saved') placed where it will be read before the agent compares siblings. Nothing in it is redundant with the title or schema.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with rich annotations and full schema coverage, most requirements are met. The remaining gap is the return contract: whether the caller receives HTML text, a URL, or a preview object, and when the plain-text branch applies, is unstated and there is no output schema to compensate.

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% and there is a single required parameter whose schema entry already reads 'Numeric id.' The description implies the id identifies a campaign but adds no format, range, or lookup semantics beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ('Renders an HTML ... preview of a campaign') and pins the scope with 'exactly as currently saved'. That phrase implicitly separates it from the draft-preview siblings, but it never names listmonk_preview_campaign_draft or listmonk_preview_campaign_text, so the agent must infer the distinction.

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?

'as currently saved' hints that this is for already-persisted campaigns rather than unsaved drafts, which is genuine usage context. However, no sibling is named and there is no explicit when-not guidance, so the routing between this, listmonk_preview_campaign_draft, and listmonk_get_campaign is left to inference.

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