Skip to main content
Glama
@kieksme/listmonk-mcp

@kieksme/listmonk-mcp

by kieksme

Manage Subscriber List Membership

listmonk_manage_subscriber_list_membership
Destructive

Manage subscriber membership in a specific Listmonk list by adding, removing, or unsubscribing selected subscribers using explicit IDs or a SQL query.

Instructions

Adds, removes, or unsubscribes subscribers from a single specific list (list_id). Select the subscribers with either an explicit ids array or a Listmonk SQL query (provide exactly one).

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": {
      "list_id": "<list_id>",
      "action": "<action>"
    },
    "name": "listmonk_manage_subscriber_list_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoSubscriber ids to modify (use this or query, not both).
queryNoListmonk SQL expression selecting subscribers (use this or ids).
actionYes
statusNoSubscription status to set when action is 'add'.
list_idYesThe list whose subscriber membership is being modified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is conveyed structurally. The description adds only the single-list scope; it does not explain what `remove` deletes versus what `unsubscribe` preserves, nor the danger of an arbitrary SQL `query` matching more subscribers than intended. Consistent with annotations, so no contradiction.

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, both front-loaded with the operation and then the selection constraint. No filler and nothing repeated that the schema already carries verbatim.

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

Completeness3/5

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

For a destructive, non-idempotent bulk mutation with no output schema, the definition is serviceable but thin: no statement of what is returned or how many subscribers were affected, no guidance on query syntax or scope-checking, and no note on how it fails for an invalid `list_id`. Annotations cover the safety profile, which keeps this at a 3 rather than lower.

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 description coverage is 80%, so the schema already documents `ids`, `query`, `status` and `list_id`, including the ids-or-query exclusivity. The description restates that exclusivity and lists the action values but adds nothing about `status` behavior or the expected SQL dialect for `query`. Baseline 3 applies.

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?

States specific verbs (adds, removes, unsubscribes), a specific resource (subscribers), and a scope constraint (a single specific list via `list_id`). The single-list scoping implicitly separates it from `listmonk_manage_subscriber_lists_bulk` and `listmonk_manage_subscriber_lists_by_query`, though neither sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds a real selection rule: provide exactly one of `ids` or `query`. But it never says when to pick this tool over `listmonk_manage_subscriber_lists_bulk` (many lists) or `listmonk_manage_subscriber_lists_by_query` (query-driven), which are the obvious alternatives for the same operation.

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