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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Mailing Lists

listmonk_list_lists
Read-onlyIdempotent

Retrieve all mailing lists with subscriber counts, optionally filtered by name, to review audiences and manage list-based campaigns.

Instructions

Lists all mailing lists with subscriber counts, optionally filtered by name.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paginated results (1-indexed).
queryNoSearch lists by name.
per_pageNoNumber of items per page (1-200, default 20).
response_formatNoOutput format: 'markdown' for human-readable text (default) or 'json' for machine-readable data.markdown

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?

The annotations already establish that the operation is read-only, non-destructive, and idempotent, while the description usefully adds that results include subscriber counts. It does not clarify that “all” is subject to paginated retrieval or add other behavioral context such as list visibility, permissions, or empty-result behavior.

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?

A single front-loaded sentence communicates the operation, scope, additional result data, and optional filter without filler. Its brevity is appropriate for a straightforward list tool.

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?

Together with the annotations and fully documented schema, the description is sufficient to invoke a simple paginated list read and select an output format. The absence of an output schema makes the limited result detail more noticeable, while sibling routing and the paginated meaning of “all” remain minor gaps.

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 100%, so page, query, per_page, and response_format are already fully documented. The description reinforces the name-search capability but adds no parameter syntax, interactions, or pagination details beyond the schema.

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 clearly states the verb and resource—“Lists all mailing lists”—and adds useful scope through subscriber counts and optional name filtering. It does not distinguish this collection operation from siblings such as listmonk_get_list or listmonk_get_public_lists.

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?

Browsing mailing lists and searching them by name are implied usage contexts. There is no explicit guidance on when to choose this tool over retrieving a single list or listing public lists, and no exclusions or prerequisites are provided.

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