@kieksme/listmonk-mcp

List Campaigns

listmonk_list_campaigns

Read-onlyIdempotent

Lists and searches campaigns with pagination, status and tag filters, sorting, and optional full bodies to locate campaigns for review or management.

Instructions

Lists/searches campaigns with pagination, status/tag filters, and sorting.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number for paginated results (1-indexed).
`tags`	No
`order`	No
`query`	No	Search campaigns by name/subject.
`status`	No
`no_body`	No	Set false to include each campaign's full HTML body.
`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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already establish a read-only, non-destructive operation, while the description adds useful context about paginated, filterable, sortable retrieval. It adds little further behavioral context, such as the default omission of campaign bodies or practical result-handling considerations.

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?

The single sentence is front-loaded with the action and resource, then efficiently lists the main controls. It contains no filler or redundant explanation.

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?

Together with the schema and annotations, the description is sufficient for an ordinary call with no required parameters. It remains minimally complete because it lacks sibling-selection guidance and practical context about the default body-light results, despite there being 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?

The description usefully groups page/per_page, status/tags, and order/order_by by purpose, but provides no matching semantics, parameter interactions, or sorting details. With 56% schema coverage and enums and defaults documenting much of the remainder, this is adequate but not especially informative.

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 actions and resource: listing or searching campaigns, with pagination, filtering, and sorting. It does not explicitly distinguish the tool from listmonk_get_campaign or other campaign-retrieval siblings.

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 and searching are implied use cases, and the named filters suggest when the tool is useful. There is no explicit guidance on when to use it versus listmonk_get_campaign, campaign preview tools, or analytics tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server