Skip to main content
Glama
@kieksme/listmonk-mcp

@kieksme/listmonk-mcp

by kieksme

List Bounces

listmonk_list_bounces
Read-onlyIdempotent

List email bounce records from Listmonk, filtered by campaign or bounce source, with pagination and sorting to inspect delivery failures.

Instructions

Lists e-mail bounce records, optionally filtered by campaign or bounce source.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paginated results (1-indexed).
orderNo
sourceNo
order_byNo
per_pageNoNumber of items per page (1-200, default 20).
campaign_idNoRestrict to bounces from a specific campaign.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds the filterable dimensions but says nothing about pagination behavior, default page size, ordering, or result volume for a tool that returns an unbounded collection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the scope qualifier follows the core action. It is efficient, though so terse that it leaves obvious operational questions unanswered rather than spending a clause on them.

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 7-parameter paginated list tool with no output schema, an agent still lacks guidance on default result size, how to page through, and what a bounce record contains. Annotations cover the read-only nature, but the collection semantics are left to the schema alone.

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 57%, so the description has to carry some weight. It clarifies that 'campaign' maps to campaign_id and that 'source' means bounce source, which is genuinely useful since the source and order/order_by parameters have no schema descriptions at all. It does not explain what the source values are or how ordering interacts with pagination.

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?

Specific verb plus resource (lists e-mail bounce records) with the scoping options named. It implicitly separates itself from listmonk_get_bounce (singular) and listmonk_get_subscriber_bounces (per-subscriber) by framing itself as the general list, but it never names those siblings explicitly.

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 phrase 'optionally filtered by campaign or bounce source' implies the browsing use case, but there is no stated when-to-use vs when-not, and no routing to listmonk_get_subscriber_bounces for per-subscriber bounce history. Usage is inferable, not instructed.

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