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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Public Lists

listmonk_get_public_lists
Read-onlyIdempotent

Retrieve the public list of subscribable mailing lists, including UUID and name, so users can view and choose available subscription options.

Instructions

Returns the public-facing list of subscribable mailing lists (uuid + name only), as seen by the public subscription page.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful scope information beyond that: only public/subscribable lists are visible and only uuid + name fields are returned, which tells the agent not to expect admin metadata. It does not cover empty results or pagination.

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?

One dense sentence with the key constraints (public, subscribable, uuid+name only) front-loaded and no filler. Slightly terse given the parenthetical field list could be integrated more cleanly, but nothing is wasted.

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 trivial read-only tool with one optional parameter and rich annotations, the definition covers purpose, scope, and the shape of the returned data. The only minor gap is behavior on empty results and confirmation that no authentication is needed.

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?

There is a single optional response_format parameter with 100% schema coverage, including an enum and default, so the schema already carries the semantics. The description adds nothing about format choice; 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 ("Returns the public-facing list of subscribable mailing lists") and narrows the scope with "public-facing", "subscribable", and "as seen by the public subscription page". This implicitly separates it from the sibling listmonk_list_lists, though it never names that alternative or the contrast 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?

The phrase "as seen by the public subscription page" implies the context in which this is the right call (public/anonymous subscribable lists rather than admin views), but there is no explicit when-to-use, when-not, or named alternative such as listmonk_list_lists.

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