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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Default Template

listmonk_set_default_template
DestructiveIdempotent

Set a template as the default for new campaigns so future campaigns use it automatically.

Instructions

Marks a template as the default template used for new campaigns.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.
response_formatNoOutput format: 'markdown' for human-readable text (default) or 'json' for machine-readable data.markdown

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=false, destructiveHint=true, and idempotentHint=true, so the safety profile is known without the description. The description reinforces the mutation but does not explain the destructive element flagged by annotations — namely that any previously default template is superseded — nor what happens if the id is invalid. It adds purpose context but not new behavioral detail.

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?

A single front-loaded sentence with zero filler that states the action and the resulting effect. Nothing is redundant or buried.

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 small two-parameter mutation with no output schema, the description covers what the tool does but not the consequences an agent would want: the previous default being replaced, error behavior for unknown ids, and confirmation of the returned state. Adequate but with clear gaps given the destructiveHint annotation.

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 description coverage is 100%, so the 'id' and 'response_format' parameters are already documented in the schema. The description mentions no parameters, adding nothing like whether the id must refer to an existing template or how response_format affects output beyond the schema's own note. 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?

The description gives a specific verb ('marks') plus resource ('template') plus the resulting state ('default template used for new campaigns'), which distinguishes it from siblings like listmonk_update_template or listmonk_create_template. It stops short of explicitly naming those siblings as alternatives, but the purpose is unambiguous.

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 implied by the outcome ('used for new campaigns'), so an agent can infer this is a settings-style toggle rather than a content edit. There is no explicit when-to-use vs. when-not guidance, no mention of using listmonk_update_template for other template changes, and no note that this is the only path to changing the campaign default.

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