Skip to main content
Glama

Honeyfield Marketing MCP

lemlist: List campaigns

lemlist_list_campaigns
Read-only

lemlist-Kampagnen auflisten, neueste zuerst. Rückgabe {"campaigns": [...]}, je Kampagne id, name, status (running/paused/draft/ended/archived/errors), created_at, labels, timezone, senders (Absender-Postfächer), leads_total (alle Leads, auch LinkedIn-only) und leads_launched (davon gestartet), errors bei Problemen. Lead-Zahlen für die 50 neuesten Kampagnen (sonst Hinweis in notes); scheitert ihr Abruf, sind sie null und lead_counts_error nennt den Grund. status: optional nur Kampagnen mit diesem Status. limit: max. 500. Kennzahlen je Zeitraum: lemlist_campaign_performance. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lemlist_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuine operational caveats beyond them: lead counts exist only for the 50 newest campaigns (otherwise a note), and failed lead fetch yields null counts with a lead_counts_error reason. Enumerating the returned fields overlaps with the existing output schema, so not a perfect 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?

The core action and ordering are front-loaded, followed by return shape, then edge-case behavior, then the sibling pointer. Dense but every clause carries information an agent needs; no filler.

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

Completeness5/5

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

For a three-parameter read tool with annotations and an output schema, the description covers the gaps that structured fields leave: filtering semantics, the 500 cap, workspace optionality, lead-count truncation at 50 campaigns, and error signaling. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry all semantics — and it does: status filters campaigns by state (with the state vocabulary listed), limit is capped at 500, workspace is a customer slug only needed with multiple workspaces. It stops short of stating limit's default of 100 or explicitly tying the status values to the filter parameter.

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?

Opens with a specific verb and resource ('lemlist-Kampagnen auflisten') plus ordering ('neueste zuerst'), and explicitly routes metric-seeking callers to the sibling lemlist_campaign_performance. An agent can distinguish this listing tool from lemlist_campaign_performance and lemlist_search_people without consulting either schema.

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?

Gives concrete conditions: status is an optional filter, limit maxes at 500, workspace is optional when only one workspace exists, and metrics over a period belong to lemlist_campaign_performance instead. Missing only an explicit statement of when not to use this tool (e.g. for lead-level data, which lemlist_list_leads covers).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources