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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Bounces

listmonk_delete_bounces
DestructiveIdempotent

Deletes bounce records in bulk, either all or specific IDs, to clean up failed email deliveries.

Instructions

Deletes bounce records in bulk — either all of them (all: true) or a specific set of ids.

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

Input Schema

NameRequiredDescriptionDefault
allNoSet true to delete ALL bounce records.
idsNoSpecific bounce ids to delete (use this or `all`).

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?

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the meaningful behavioral distinction that the operation can be scoped to all records or a specific set, which signals the blast radius of `all: true`. It does not warn about irreversibility or suggest confirmation for the all-records case.

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?

A single sentence with the operation front-loaded and the two modes immediately after. Nothing is redundant or padded.

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 two-parameter destructive tool with rich annotations and no output schema, the definition covers the core invocation shapes. However, required parameters is zero, and the description never says what happens if neither `all` nor `ids` is supplied — no-op, error, or full delete — which is the key ambiguity an agent needs resolved before calling.

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 both parameters carry their own descriptions, so the schema already does the explanatory work. The description restates the same all-versus-ids choice without adding syntax, limits, or precedence rules beyond what the schema provides.

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 ('Deletes') and resource ('bounce records') plus a scope qualifier ('in bulk'), which implicitly separates it from the single-record sibling listmonk_delete_bounce. It stops short of naming the sibling explicitly, so an agent must infer the split from the word 'bulk'.

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: the two modes (`all: true` vs `ids`) are stated, and the schema notes they are alternatives. There is no explicit 'use listmonk_delete_bounce for a single record' routing and no guidance on when bulk deletion is appropriate versus using a query-based sibling.

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