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

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Campaign

listmonk_create_campaign

Creates a draft campaign for selected lists so you can review it before explicitly scheduling or starting it through the status update tool.

Instructions

Creates a new campaign as a draft. Drafts must be explicitly scheduled/started via listmonk_update_campaign_status.

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": {
      "name": "<name>",
      "subject": "<subject>",
      "lists": "<lists>"
    },
    "name": "listmonk_create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
nameYes
tagsNo
typeNoregular
listsYesList ids to send this campaign to.
send_atNoISO 8601 timestamp; requires send_later: true.
subjectYes
messengerNoemail
from_emailNo
send_laterNo
template_idNo
content_typeNorichtext
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description earns credit for the genuinely non-obvious behavior that the created object is inert until explicitly started via listmonk_update_campaign_status. It does not disclose whether validation errors reject the whole call, what content (body vs template_id) is required, or whether the new campaign's id is returned.

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, front-loaded with the primary effect and followed by the lifecycle constraint. No filler, no restatement of the title.

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?

For a 13-parameter creation tool with 23% schema coverage and no output schema, the description is thin. It omits what must be supplied to make a usable draft and whether the response yields the campaign id needed for the follow-up status call, which is the natural next action it recommends.

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 23% across 13 parameters, so the description carries the burden of explaining them and adds nothing. Key semantics are left undocumented, notably the send_later/send_at pairing, the interplay of body, content_type and template_id, and from_email defaults. Only lists, send_at and response_format have schema descriptions at all.

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 and resource ("Creates a new campaign") and immediately narrows the outcome to a draft, which separates it from listmonk_update_campaign and the preview/send siblings. It does not enumerate what the other campaign-creation-adjacent tools do, but the draft qualifier is enough for an agent to pick this one.

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 rather than stated: you call this to stage a campaign, then call listmonk_update_campaign_status to schedule or start it. The forward reference is useful, but there is no explicit when-not guidance, no mention that the required name/subject/lists must be known up front, and no pointer to listmonk_preview_campaign_draft before sending.

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