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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Campaign Archive Settings

listmonk_update_campaign_archive
DestructiveIdempotent

Publishes or unpublishes a campaign on Listmonk's public archive page, controlling archive visibility with optional slug, template, and metadata.

Instructions

Publishes or unpublishes a campaign to Listmonk's public campaign archive page.

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>",
      "archive": "<archive>"
    },
    "name": "listmonk_update_campaign_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.
archiveYesWhether this campaign is published to the public archive.
archive_metaNo
archive_slugNoURL slug for the archived campaign page.
archive_template_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds useful context that the effect is public visibility on the archive page, but it never explains what unpublishing does to the live public URL, nor that archive_slug/archive_template_id/archive_meta are also written by this call.

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 front-loaded sentence of roughly fifteen words, with zero filler or redundancy. It is efficient, though the brevity contributes to the gaps in the other dimensions rather than reflecting completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, open-world mutation with five parameters, a nested object, and no output schema, yet the description covers only the top-level toggle. An agent gets no guidance on the optional archive_slug/archive_template_id/archive_meta fields or on the consequences of unpublishing, which is inadequate for the tool's complexity.

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 coverage is only 60%, and two parameters (archive_meta and archive_template_id) have no description anywhere, while archive_slug has only a terse schema line. The description mentions no parameters at all, so it does nothing to compensate for the coverage gap or to explain how the optional fields interact with the archive toggle.

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 states a concrete action (publishing/unpublishing) on a specific resource (a campaign's entry on Listmonk's public campaign archive page), which is more precise than the title's generic 'Update Campaign Archive Settings'. It distinguishes itself reasonably well from listmonk_update_campaign and listmonk_update_campaign_status, though it never names those siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of how this differs from listmonk_update_campaign, no prerequisites (campaign must exist, archive feature enabled), and no note on when to unpublish versus delete. The agent must infer routing from the name alone.

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