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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export Subscriber Data

listmonk_export_subscriber
Read-onlyIdempotent

Exports a subscriber's full profile—personal data, list memberships, and campaign views—as JSON for GDPR data-subject access requests.

Instructions

Exports a subscriber's full profile (personal data, list memberships, campaign views) as a JSON object, e.g. for GDPR data-subject access requests.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description earns credit for adding what the annotations cannot: the output is a JSON object aggregating profile, membership and campaign-view data. It omits failure behavior for an unknown id, which keeps it from a 5.

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?

One sentence that front-loads the verb and resource, then lists the payload contents, with the use case trailing as a qualifier. Nothing is redundant or padded.

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 one-parameter read with no output schema, the description is the only source of return-shape information and it names the three data categories returned. It could still clarify how this differs from listmonk_get_subscriber and what happens on an invalid or missing id.

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 required integer id with 100% schema description coverage, so the schema already carries parameter meaning. The description only implies 'identified by id' through 'a subscriber's', adding no format or lookup nuance beyond the schema; 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?

The description gives a specific verb ('Exports') and resource ('a subscriber's full profile') and enumerates what the export contains (personal data, list memberships, campaign views). It distinguishes itself only implicitly from the sibling listmonk_get_subscriber by the word 'full' and the enumerated contents; an explicit contrast would be needed for a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It supplies a concrete use case ('for GDPR data-subject access requests'), which tells an agent when this tool is the right pick rather than a routine single-field lookup. It does not explicitly name listmonk_get_subscriber as the lighter alternative or state exclusions, so it stops short of full routing guidance.

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