@kieksme/listmonk-mcp

Delete Media

listmonk_delete_media

DestructiveIdempotent

Permanently delete an uploaded Listmonk media file by its numeric ID to remove unwanted files from your media library.

Instructions

Permanently deletes an uploaded media file 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_delete_media"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 4, 2026

TDQS

A3.6/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 largely covered. The word 'Permanently' usefully confirms irreversibility beyond the boolean hint, but the description says nothing about error behavior on a missing id, whether the underlying file is removed from storage, or whether repeated calls succeed silently.

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?

One short sentence with the irreversibility warning front-loaded, and no filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with rich annotations and a fully covered schema, the definition supplies what an agent minimally needs. It stops short of describing downstream effects on content that references the media file, which would have made it complete for a destructive operation.

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 a single integer 'id' parameter that the schema documents as a positive numeric id. The description's 'by id' merely restates that, adding no format, sourcing, or lookup guidance beyond what the schema gives, so the baseline 3 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?

States a specific verb and resource ('Permanently deletes an uploaded media file'), and the 'by id' qualifier pins the scope. It is clearly separable from siblings like listmonk_get_media, listmonk_list_media, and listmonk_upload_media, though it does not name them.

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 operation identifies a media file for removal, so the agent can infer 'call when you want a media file gone.' There is no explicit when-not guidance, no suggestion to verify the id via listmonk_get_media first, and no mention of what happens if the file is still referenced by a campaign or template.

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

Deploy Server