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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Subscriber Bounces

listmonk_get_subscriber_bounces
Read-onlyIdempotent

Retrieves bounce records for a single subscriber by numeric ID, helping you diagnose delivery failures and review which messages bounced.

Instructions

Lists bounce records recorded for a single subscriber.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.
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.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds nothing on top of that – no pagination behaviour, no ordering of returned bounces, no indication of what happens for a subscriber with no bounces.

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?

A single tight sentence with no filler and the scope qualifier front-loaded. It is efficient, though the brevity borders on under-specification rather than optimal trimming.

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, annotation-covered read tool with fully documented parameters and no output schema, the description is minimally viable. It still leaves an agent guessing about result volume/pagination and about the id-type ambiguity against listmonk_get_bounce.

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% with both parameters ('id' and the markdown/json 'response_format') documented in the schema itself, so the baseline of 3 applies. The description does not clarify that 'id' must be a subscriber id rather than a bounce id – a distinction that matters given the sibling listmonk_get_bounce takes a bounce id.

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 gives a specific verb ('Lists') and resource ('bounce records') and adds a scope qualifier ('recorded for a single subscriber') that implicitly distinguishes it from listmonk_list_bounces and listmonk_get_bounce. It does not name those siblings outright, so an agent must infer the boundary rather than being told it.

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?

Usage is only implied by the scoping phrase 'for a single subscriber' – that is enough to know it targets one subscriber's bounce history. There is no explicit when-to-use/when-not guidance and no pointer to listmonk_list_bounces for an account-wide bounce listing or to listmonk_delete_subscriber_bounces for the matching mutation.

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