@kieksme/listmonk-mcp

Get Bounce

listmonk_get_bounce

Read-onlyIdempotent

Retrieve a single Listmonk bounce record by ID to inspect delivery failure details. Returns the record in markdown or JSON for troubleshooting and reporting.

Instructions

Retrieves a single bounce record by id.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric id.
`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

C2.9/5.0

Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that: no note on error behavior for an invalid or missing id, no indication of what the returned record contains, and no scoping/pagination context. With a lower bar due to annotations, this still fails to add value.

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?

It is a single, front-loaded sentence with zero wasted words. The economy is suitable, though the terseness borders on under-specification rather than polished conciseness.

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 single-record getter with rich annotations, full schema coverage, and no output schema, the description covers the core action. However, it omits anything about what a bounce record represents, error handling for a missing id, or how it relates to the bounce-listing tools, leaving an agent to infer the surrounding workflow.

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 both the id and response_format parameters are already documented in the schema, including the enum for output format. The description's phrase "by id" merely restates the required parameter and adds no syntax, format, or constraint detail. Baseline 3 is appropriate.

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?

States a specific verb ("Retrieves") and resource ("a single bounce record") scoped by id, so an agent can distinguish it from a bulk bounce listing. It stops short of naming or contrasting any sibling tool such as listmonk_list_bounces, so it is clear but not differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no pointer to an alternative tool for listing or deleting bounces. The only hint is the phrase "by id," which faintly implies a lookup, but nothing states the conditions under which this tool is the right choice over listmonk_list_bounces or listmonk_get_subscriber_bounces.

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

Deploy Server