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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Subscriber

listmonk_get_subscriber
Read-onlyIdempotent

Retrieves a single subscriber by numeric ID, including their list memberships, so you can inspect one contact and the lists they belong to.

Instructions

Retrieves a single subscriber by numeric id, including their list memberships.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description does add one genuine payload detail — that list memberships are included — which is useful given there is no output schema, but it omits error behavior for a nonexistent id and says nothing about the response_format choice's effect on the payload.

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 key lookup mechanism is stated immediately. It is efficient, though its brevity borders on under-specification rather than optimal completeness.

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?

This is a simple two-parameter read tool with full schema coverage and rich annotations, so little explanation is strictly required. Still, an agent is left without guidance on what happens when the id does not exist or how markdown vs json affects the returned content, which are the two remaining practical gaps.

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 both the id and response_format parameters are already documented in structured form; the baseline of 3 applies. The description's 'numeric id' merely echoes the schema's integer type and adds no constraint or format detail beyond it, and it says nothing about response_format.

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 ('Retrieves a single subscriber') plus the lookup key (numeric id), which clearly distinguishes it from list_subscribers and create/update/delete_subscriber siblings. It does not explicitly name the alternative to use for filtered listing, but the singular-vs-plural distinction is unambiguous.

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 'single subscriber by numeric id' — an agent can infer it should be used when it already has an id rather than search criteria. There is no explicit when-to-use/when-not statement, no mention of alternatives such as listmonk_list_subscribers, and no note that membership management has its own dedicated tools.

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