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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Subscribers By Query

listmonk_delete_subscribers_by_query
Destructive

Permanently deletes all Listmonk subscribers matching a SQL query expression in one bulk, irreversible operation. Verify the match count first with the same query.

Instructions

BULK, IRREVERSIBLE, NO-PREVIEW: permanently deletes every subscriber matching a Listmonk SQL query expression. Always call listmonk_list_subscribers with the same query first to confirm the match count before using this tool.

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": {
      "query": "<query>"
    },
    "name": "listmonk_delete_subscribers_by_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesListmonk SQL expression selecting subscribers to permanently delete. THIS IS A BULK, IRREVERSIBLE, NO-PREVIEW OPERATION. Always call listmonk_list_subscribers with the same query first to verify the exact match count before calling this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds what annotations cannot: that the operation is BULK-scoped (every matching record, not one), has NO-PREVIEW, and is IRREVERSIBLE. It does not say what the response reports or whether list memberships/bounces cascade, which is the remaining behavioral gap.

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, zero filler, and the danger is front-loaded in capitals before the procedural instruction. Ordering matches the risk: severity first, mitigation second.

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 destructive tool with annotations covering the safety profile and no output schema, the description supplies the missing bulk/irreversible semantics and the verification step. It could have noted whether the match count is returned or what happens to related records, but nothing essential to invoking it safely is absent.

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 single `query` parameter is documented in the schema with essentially the same warning wording used in the description. The description adds no syntax, quoting, or expression-shape guidance beyond what the schema already supplies, so baseline 3 applies.

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 and resource (permanently deletes every subscriber) plus the exact selector mechanism (a Listmonk SQL `query` expression). The bulk-by-query scope is explicit enough to separate it from listmonk_delete_subscriber and listmonk_delete_subscribers_by_ids without opening any schema.

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 a concrete precondition workflow: call listmonk_list_subscribers with the same query first to confirm the match count. That is real when-to-use guidance naming a sibling tool. It stops short of choosing between this and listmonk_delete_subscribers_by_ids, or of saying when bulk-by-query is inappropriate.

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