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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Upload Media

listmonk_upload_media

Upload image files to the Listmonk media library for use in campaigns and templates.

Instructions

Uploads an image file to the media library for use in campaigns/templates.

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": {
      "file_name": "<file_name>",
      "file_content_base64": "<file_content_base64>"
    },
    "name": "listmonk_upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameYesOriginal filename incl. extension, e.g. 'banner.png'.
content_typeNoMIME type, e.g. 'image/png'. Guessed from extension if omitted.
response_formatNoOutput format: 'markdown' for human-readable text (default) or 'json' for machine-readable data.markdown
file_content_base64YesBase64-encoded file bytes.

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?

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond that: it does not state size limits, whether re-uploading the same filename duplicates or overwrites (relevant given idempotentHint=false), or what the server returns on success.

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 the verb first and no filler. It is efficient, though its brevity means the space saved is not reinvested in constraints an agent would need.

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 four-parameter upload with a fully documented schema and no output schema, the description is minimally sufficient. It still leaves out accepted formats/size limits and the shape of the result (asset ID or URL), which an agent needs to chain into campaign or template calls.

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 all four parameters documented in-schema, including the base64 payload, filename-with-extension requirement, MIME type guessing, and response_format enum. The description adds no parameter-level meaning, so the baseline of 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 ('Uploads') and resource ('an image file to the media library') plus the downstream purpose (campaigns/templates). Among siblings it is clearly the only upload path versus list_media, get_media, and delete_media, though 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 Guidelines3/5

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

Usage is implied by 'for use in campaigns/templates', which tells an agent why it would call this. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as authentication or library permissions, and no pointer to alternatives like reusing an existing asset via get_media.

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