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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Blocklist Subscribers By Query

listmonk_blocklist_subscribers_by_query
Destructive

Bulk-blocklists all subscribers matching a Listmonk SQL query expression; verify the match count with listmonk_list_subscribers first to avoid unintended blocks.

Instructions

BULK, NO-PREVIEW: blocklists every subscriber matching a Listmonk SQL query expression. Always call listmonk_list_subscribers with the same query first to confirm the match count.

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

Input Schema

NameRequiredDescriptionDefault
queryYesListmonk SQL expression selecting subscribers to blocklist in bulk. Always call listmonk_list_subscribers with the same query first to verify the match count.

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 declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds the crucial operational fact that there is no preview/dry-run and that the operation is bulk, which is exactly the context an agent needs before an irreversible mass mutation.

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 risk qualifier (BULK, NO-PREVIEW) followed by the required pre-check. No wasted wording.

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 full annotation coverage, the description covers the main risk and the verification workflow. It does not mention whether blocklisting is reversible or what the call returns, a minor gap given there is no output schema.

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 parameter's description already contains the same verification guidance. The description adds only the framing of `query` as a Listmonk SQL expression, so it does not meaningfully exceed the schema.

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 (blocklists), the resource (every subscriber matching a SQL query), and the scope (BULK, NO-PREVIEW). This clearly separates it from listmonk_blocklist_subscriber (single) and listmonk_blocklist_subscribers_bulk (by IDs).

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?

Explicitly instructs calling listmonk_list_subscribers with the same query first to confirm match count, which is a concrete prerequisite. It does not name the sibling blocklist-by-IDs tool as an alternative, so routing between the two bulk variants is left implicit.

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