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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Media

listmonk_list_media
Read-onlyIdempotent

Lists uploaded media files used in campaigns and templates, with pagination and filename search so you can find and manage images.

Instructions

Lists all uploaded media files (images used in campaigns/templates).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paginated results (1-indexed).
queryNoSearch media filenames.
per_pageNoNumber of items per page (1-200, default 20).
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?

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only a definition of media content; it says nothing about pagination behavior, result ordering, empty-result handling, or output shape, and its phrase "all uploaded media files" slightly obscures that results are paginated and filterable.

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 front-loaded sentence with no filler and the resource in the first few words. It is efficient, though the parenthetical could instead have carried operational information such as pagination or the search capability.

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

Completeness5/5

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

For a simple read-only list endpoint with four optional, fully documented parameters and no output schema, the definition covers the essentials: what is listed and what the items represent. The remaining details, pagination and return format, are fully specified in the schema and annotations.

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 page, query, per_page, and response_format are already fully documented. The description adds no parameter meaning and does not mention that a filename search or page size can be supplied, leaving the schema to do all the work — 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 ("Lists all uploaded media files") and clarifies what media means here (images used in campaigns/templates). It is clearly distinct from listmonk_get_media, listmonk_upload_media, and listmonk_delete_media, but it never names those siblings explicitly.

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 and no reference to alternatives such as listmonk_get_media for a single item. The agent must infer that this is the bulk-retrieval counterpart to get_media from the name alone.

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