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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Garbage-Collect Campaign Analytics

listmonk_delete_gc_campaign_analytics
Destructive

Permanently deletes campaign analytics records—views, clicks, or all—older than a specified RFC3339 date. Use to purge old Listmonk analytics; irreversible, so confirm before calling.

Instructions

PERMANENTLY DELETES campaign analytics records (views/clicks/all) older than a given date. Irreversible; confirm with the user before calling.

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": {
      "type": "<type>",
      "before_date": "<before_date>"
    },
    "name": "listmonk_delete_gc_campaign_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhich class of campaign analytics to permanently delete.
before_dateYesDelete records older than this RFC3339 timestamp, e.g. '2024-01-01T00:00:00Z' (not just a date).

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 flag destructiveHint=true and readOnlyHint=false, but the description adds real value: the deletion is permanent/irreversible and requires user confirmation. It stops short of saying what is returned (e.g., a count of purged rows) or what happens on a partial/failed purge.

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 short sentences, zero filler, and the destructive nature is front-loaded in capitals so an agent cannot miss it before parsing the rest.

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 two-parameter destructive tool with full schema coverage and no output schema, the definition covers the essentials: what is destroyed, the scope, irreversibility, and the confirmation requirement. The only gaps are the return value (deletion count) and reinforcing the RFC3339 timestamp format.

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 coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description echoes the enum values ('views/clicks/all') and the date cutoff, but adds no syntax detail; notably it says 'date' while the schema requires a full RFC3339 timestamp.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('PERMANENTLY DELETES'), a specific resource ('campaign analytics records'), and a scope ('older than a given date'). This clearly distinguishes it from read-only siblings such as listmonk_get_campaign_analytics and from the other GC tools.

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?

Provides a caller-side rule ('confirm with the user before calling') but no when-to-use/when-not guidance or named alternatives. It never says to inspect analytics via listmonk_get_campaign_analytics first, nor how this differs from other purge tools like listmonk_delete_bounces or listmonk_delete_gc_subscribers.

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