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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Running Campaign Stats

listmonk_get_running_campaign_stats
Read-onlyIdempotent

Retrieve live send-rate statistics for all currently running campaigns, so you can monitor delivery progress and spot issues in real time.

Instructions

Returns live send-rate statistics for all currently running campaigns.

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

Input Schema

NameRequiredDescriptionDefault
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.5/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, idempotent, non-destructive, and open-world. The description adds useful live-data and all-running-campaigns scoping, but does not clarify refresh or snapshot behavior, included metrics, or what happens when no campaigns are running.

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 direct, front-loaded, and free of filler. It efficiently preserves the important qualifiers: live, send-rate, all, and currently running.

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 simple read with no required parameters, this is enough to understand the broad operation and invoke it. However, with no output schema, the lack of detail about returned statistics and the absence of differentiation from campaign analytics leave noticeable selection and interpretation 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%, and the sole response_format parameter already documents its enum values, default, and intended uses. The description adds no parameter meaning beyond that complete schema, so the baseline score 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?

The description clearly states the verb, resource, and scope: live send-rate statistics for all currently running campaigns. The qualifiers help distinguish it from general campaign listing, but the boundary with listmonk_get_campaign_analytics is not explicitly explained.

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?

The wording implies use for live monitoring of running campaigns rather than retrieving campaign configuration or historical statistics. It provides no explicit when-not guidance or alternative, such as listmonk_get_campaign_analytics for other campaign analytics.

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