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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Template

listmonk_delete_template
DestructiveIdempotent

Permanently delete a Listmonk template by ID, with the default template protected from deletion.

Instructions

Permanently deletes a template by id. The default template cannot be deleted.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.

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 destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is carried structurally. The description adds value the annotations do not: the permanence of the deletion and the server-side guard against deleting the default template. It omits the downstream consequence of deletion, such as what happens to campaigns referencing the template.

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 short sentences, zero filler, with the core action and its permanence front-loaded and the blocking constraint second. Nothing repeats the schema or the annotations.

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 one-parameter delete whose destructive and idempotent flags are already declared and which has no output schema, the description covers the essentials plus the key guard. The only meaningful gap is the effect on campaigns that reference the deleted template, which would matter to an agent deciding whether to proceed.

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% with a single required integer 'id', so the baseline is 3. The phrase 'by id' confirms the identifier is a template id rather than a name or slug, but adds no format, range, or lookup guidance beyond the schema's 'Numeric id.'

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 and resource ('Permanently deletes a template') plus the lookup key ('by id'), which cleanly separates it from listmonk_get_template, listmonk_update_template, and the delete tools for campaigns, lists, and media. It stops short of naming or contrasting a sibling, but the resource 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?

The default-template exclusion gives one concrete precondition that tells the agent when this call will fail, which is real usage guidance. There is no explicit statement of when to prefer delete over update, archive, or set_default_template, and no mention of confirmation or irreversibility policy, so usage is only implied.

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