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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Garbage-Collect Subscribers

listmonk_delete_gc_subscribers
Destructive

Permanently deletes blocklisted or orphan subscribers (those with no list memberships) to clean up Listmonk subscriber data; irreversible, so confirm before use.

Instructions

PERMANENTLY DELETES subscribers matching a maintenance class ('blocklisted' or 'orphan' — subscribers with no list memberships). Irreversible; confirm with the user before calling.

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": {
      "type": "<type>"
    },
    "name": "listmonk_delete_gc_subscribers"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhich class of subscribers to permanently delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotence, but the description adds a procedural requirement (confirm with the user before calling) and clarifies that 'orphan' means no list memberships, which the annotations do not convey. It stops short of stating the scale of deletion or whether a count is returned.

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, front-loaded with the destructive nature and the exact accepted classes. Every clause carries information an agent needs before calling.

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?

For a single-parameter, non-idempotent destructive tool with no output schema, the description covers what is deleted, the allowed classes, irreversibility, and the confirmation obligation. Nothing needed to invoke it safely is missing.

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 the enum is already constrained, so the schema does most of the work. The description adds a small amount of meaning by explaining that 'orphan' equals subscribers with no list memberships, which the schema's one-line description does not define.

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 (PERMANENTLY DELETES) and resource (subscribers matching a maintenance class), and enumerates the only two classes. This clearly separates it from listmonk_delete_subscriber, listmonk_delete_subscribers_by_ids, and listmonk_delete_subscribers_by_query, which target explicit identities or queries rather than a class.

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 the selecting condition (subscribers matching 'blocklisted' or 'orphan'), which is the main ambiguity an agent would face. It does not explicitly say when to prefer this over listmonk_delete_subscribers_by_query or listmonk_blocklist_subscribers_bulk, so the routing is inferred rather than spelled out.

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