@kieksme/listmonk-mcp

Get Media

listmonk_get_media

Read-onlyIdempotent

Retrieve metadata for a single uploaded media file by its numeric ID from a Listmonk instance.

Instructions

Retrieves metadata for a single 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_get_media"
  }
}

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

A3.8/5.0

Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive, open-world operation. The description adds the useful detail that only metadata is retrieved rather than the media bytes, but it does not address not-found behavior, permissions, or other runtime characteristics.

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?

The single sentence is front-loaded with the operation and contains no filler. It efficiently conveys the resource, cardinality, returned information type, and lookup key without repeating parameter documentation.

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 simple two-parameter getter with complete schema documentation and read-only annotations, this is sufficient for selection and invocation in the common case. It could be more complete by pointing to listmonk_list_media for ID discovery and, since there is no output schema, giving some indication of the returned metadata or not-found behavior.

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 id and response_format are clearly documented there, warranting the baseline score. The phrase 'by id' reinforces the identifier's role but adds no semantics beyond the schema, and the description does not discuss response_format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource and narrows the operation to metadata for one uploaded file identified by ID. That scope distinguishes it from listmonk_list_media and the upload/delete siblings, while also signaling that it does not download the file's binary content.

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 wording implies that the tool is appropriate when the media ID is already known and only one record is needed. It provides no explicit alternative, such as using listmonk_list_media to browse media or discover an ID, so the selection guidance remains inferential.

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

Deploy Server