@kieksme/listmonk-mcp

List Subscribers

listmonk_list_subscribers

Read-onlyIdempotent

List and search Listmonk subscribers with pagination, sorting, SQL filters, and list membership. Find subscriber IDs and preview match counts before bulk operations.

Instructions

Lists/searches subscribers with pagination, sorting, and an optional Listmonk SQL filter expression (query) or list membership filter. Use this to find subscriber ids before calling other subscriber tools, and to preview the match count of a query before running a bulk query-based operation (delete/blocklist/list-membership).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listmonk_list_subscribers"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number for paginated results (1-indexed).
`order`	No
`query`	No	Filter subscribers with a Listmonk SQL expression over the subscribers table, e.g. "subscribers.email LIKE '%@example.com'". Omit to list all.
`list_id`	No	Restrict to subscribers of these list ids.
`order_by`	No
`per_page`	No	Number of items per page (1-200, default 20).
`response_format`	No	Output format: 'markdown' for human-readable text (default) or 'json' for machine-readable data.	markdown
`subscription_status`	No	Only applies when list_id is given.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior. The description adds real value beyond them: the filter is a raw Listmonk SQL expression over the subscribers table, and this listing can be used to preview match counts before destructive bulk operations. It doesn't say whether the query string is interpolated safely or what total/count metadata 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 dense sentences, no filler, with the capability statement front-loaded and the usage guidance following. Every clause carries information an agent needs.

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 an 8-parameter, no-required-argument list tool with no output schema, the description covers purpose, filtering modes, and pagination well enough to invoke it correctly. It could be slightly stronger on the shape of the returned data (counts vs. items) 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 75%, so most parameters are self-documenting. The description adds that `query` is a Listmonk SQL filter expression and that list membership is an alternative filter path, but says nothing about the undescribed enum params (order, order_by) or their defaults, leaving a gap the schema doesn't fill.

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 ('Lists/searches') and resource ('subscribers'), plus the scoping axes (pagination, sorting, query filter, list membership). The final clause about finding subscriber ids makes clear how this read tool relates to the mutation siblings.

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 two concrete use cases: resolving subscriber ids for other tools, and previewing the match count of a `query` before a bulk query-based delete/blocklist/membership operation, which maps to the *_by_query siblings. It stops short of saying when to prefer get_subscriber or when a plain list of all subscribers 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