Skip to main content
Glama

Honeyfield Marketing MCP

lemlist: Set lead interest

lemlist_set_lead_interest
Destructive

Lead in einer lemlist-Kampagne als interessiert (interested=True) oder nicht interessiert (False) markieren, z. B. nach einer Antwort. lead_id aus lemlist_list_leads bzw. lemlist_list_replies. Rückgabe: before/after (status, state), verified. Braucht die Freigabe „Lead-Daten freigeben“ im Workspace (Portal). workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "campaign_id": "<campaign_id>",
      "lead_id": "<lead_id>",
      "interested": "<interested>"
    },
    "name": "lemlist_set_lead_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYes
workspaceNo
interestedYes
campaign_idYes
validate_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description only needs to add context. It does: it names the required workspace permission 'Lead-Daten freigeben' and discloses that the response contains before/after status/state plus a verification flag, which tells the agent the prior value is captured. It never explicitly warns that an existing interest classification is overwritten, which is the main residual gap.

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?

Front-loaded with the action, then prerequisites, then parameter hints. Compact and free of filler; only minor cost is that permission and parameter notes are packed into separate lines without much structure.

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

Completeness3/5

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

Covers purpose, permission prerequisite and effect verification, and the output schema covers return shape. But with zero schema description coverage and no annotations-level detail on overwrite behavior, an agent still lacks semantics for a required parameter (campaign_id) and for validate_only.

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 description coverage is 0%, so the description carries the full burden. It explains lead_id (source tools), interested (True/False semantics) and workspace (optional when only one workspace), but leaves campaign_id (required) and validate_only completely undocumented in both schema and description.

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?

States a specific verb and resource: mark a lead in a lemlist campaign as interested (True) or not interested (False). Clear enough to act on, but it does not explicitly distinguish itself from the nearest sibling, lemlist_set_lead_paused, which is another per-lead state mutation in the same campaign.

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 a concrete triggering context ('z. B. nach einer Antwort') and tells the agent where lead_id comes from (lemlist_list_leads / lemlist_list_replies). No explicit when-not-to-use guidance or statement of how this differs from pausing a lead.

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