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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage Subscriber Lists By Query

listmonk_manage_subscriber_lists_by_query
Destructive

Bulk add, remove, or unsubscribe subscribers matching a Listmonk SQL query from target lists; confirm the match count before applying changes.

Instructions

BULK, NO-PREVIEW: adds, removes, or unsubscribes every subscriber matching a Listmonk SQL query expression from one or more target lists. 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>",
      "action": "<action>",
      "target_list_ids": "<target_list_ids>"
    },
    "name": "listmonk_manage_subscriber_lists_by_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesListmonk SQL expression selecting subscribers to modify in bulk. Always call listmonk_list_subscribers with the same query first to verify the match count.
actionYes
statusNoSubscription status to set when action is 'add'.
target_list_idsYes

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, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description usefully adds that the operation is bulk with no preview and that a count-verification step should precede it, but it never says whether removals/unsubscribes are reversible or how many records is too many for one call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the highest-risk fact ('BULK, NO-PREVIEW') is front-loaded before the mechanics. The structure is close to ideal for a destructive tool, though the ALL-CAPS framing borders on noise.

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 destructive, non-idempotent, open-world bulk mutation with no output schema, the description supplies the one thing an agent most needs: verify the match set first. A note on reversibility or result reporting would make it fully complete, but the essentials are present.

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 50%: query and status have their own descriptions, while action and target_list_ids do not. The description compensates partially by enumerating the three actions' effects and noting multiple target lists, but adds nothing about list ID format or query syntax limits beyond what the schema already states.

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?

The description gives a specific verb set (adds, removes, unsubscribes), a precise resource scope (every subscriber matching a Listmonk SQL query expression), and a target (one or more lists). The 'BULK, NO-PREVIEW' prefix separates it from single-record tools like listmonk_manage_subscriber_list_membership, though it never names the by-IDs sibling it competes with.

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?

It states an explicit prerequisite: always call listmonk_list_subscribers with the same query first to confirm the match count. That is real when-to-use guidance, but it gives no guidance on choosing this over listmonk_manage_subscriber_lists_bulk (IDs) or listmonk_blocklist_subscribers_by_query.

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