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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Public Subscription

listmonk_create_public_subscription

Submits a visitor-style public subscription request to Listmonk, adding an email to chosen lists and triggering double opt-in emails where required.

Instructions

Submits a subscription request via Listmonk's public (unauthenticated) subscription endpoint, as if a visitor filled out the public sign-up form. Triggers double opt-in e-mails for lists that require them.

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": {
      "email": "<email>",
      "list_uuids": "<list_uuids>"
    },
    "name": "listmonk_create_public_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailYes
list_uuidsYesUUIDs of the public lists to subscribe to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, open-world write, and the description adds real context beyond that: the endpoint is unauthenticated and the call will trigger double opt-in e-mails for lists that require them. That e-mail side effect is exactly the kind of consequence an agent needs before invoking. It does not describe the response or failure modes for already-subscribed addresses.

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?

Two sentences, front-loaded with the action and endpoint, followed by the side effect. Nothing is redundant and every clause carries information.

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 three-parameter, no-output-schema tool, the description covers what it does, its unauthenticated nature, and its e-mail consequence — enough to call it correctly. The missing piece is what a successful call returns (confirmation state) and how to handle an address already on the list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — list_uuids is documented and email carries a format/pattern, but name has no description anywhere. The description adds no parameter-level meaning (no note that list_uuids must be public lists, no explanation of what name is used for), so it fails to compensate for the coverage gap.

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?

The description names a specific verb and resource ("Submits a subscription request") and pins the mechanism (Listmonk's public subscription endpoint), which clearly separates it from the authenticated admin-side subscriber tools. It stops short of naming a sibling such as listmonk_create_subscriber, so the contrast is implied rather than explicit.

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?

"As if a visitor filled out the public sign-up form" implies the scenario (public-facing sign-up) but never states when to prefer this over listmonk_create_subscriber or listmonk_import_subscribers. No exclusions or prerequisites are given, leaving the agent to infer the public-vs-admin distinction.

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