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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reload Listmonk App

listmonk_reload_app
Destructive

Restarts Listmonk's app process and background workers after settings changes; briefly interrupts campaign sending and API availability, so confirm before use.

Instructions

Restarts Listmonk's background workers/app process (used after certain settings changes). Briefly interrupts campaign sending and API availability. Confirm with the user before calling.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listmonk_reload_app"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds blast-radius context the annotations cannot convey: the interruption is brief and affects both campaign sending and API availability. It also adds a consent requirement. It stops short of saying whether in-flight work resumes or is lost.

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?

Three short sentences, front-loaded with the action, then impact, then the safety instruction. Every clause carries information an agent needs before invoking a destructive, non-idempotent operation; nothing is redundant.

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

Completeness5/5

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

With zero parameters, no output schema, and annotations carrying the safety profile, the remaining burden is explaining impact and timing — which the description does. An agent has everything required to decide whether to call it and to warn the user about the brief outage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4; there is nothing for the description to add and it correctly introduces no parameter discussion. Schema coverage is reported at 100% for an empty object, so no compensation is needed.

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 ("Restarts") and resource ("Listmonk's background workers/app process"), and the parenthetical scope note clarifies exactly what gets restarted. None of the sibling tools perform a process reload, so the distinction is inherent, but the description still pins the target precisely.

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?

"Used after certain settings changes" tells the agent the triggering condition, and "Confirm with the user before calling" adds an explicit pre-call gate. It does not name a concrete alternative or say when-not to call (e.g., during an active send), so it falls just 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