Leadpoet

Remove contacts not yet messaged

removeUnmessagedCampaignContacts

DestructiveIdempotent

Removes every contact in a paused campaign who was never messaged, or the listed contacts, one company's contacts, or those matching audience filters, and removes their unsent drafts and queued sends. They can then join another campaign but never this one again. Contacts who were messaged stay. remaining says how many could still leave; repeat while removed is above zero. Repeating the call with the same input leaves the same result.

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": {
      "params": "<params>"
    },
    "name": "removeUnmessagedCampaignContacts"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses what is destroyed, namely unsent drafts and queued sends, and that removed contacts can join another campaign but never this one again. It also explains the remaining/removed repeat behavior and confirms idempotency, which is consistent with the annotations.

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 description is front-loaded with the core action and consequence, and every sentence adds operational meaning. There is no filler or repetition.

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 destructive, nested-parameter tool with no output schema, the description covers the main consequences, idempotency, and repeat condition well. It leaves some filter-level parameter semantics to the schema, which is a minor gap given the overall disclosure.

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?

With 0% schema description coverage, the description helps by explaining the high-level targeting modes represented by body.company, body.filters, and body.enrollment_ids, and it implies params.id identifies the campaign. However, it does not map individual filter fields or clarify the nested filters object in detail.

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?

The description states a specific verb and resource: it removes campaign contacts who were never messaged, along with their unsent drafts and queued sends. It also distinguishes the tool from the read-only sibling getUnmessagedCampaignContacts by emphasizing removal and the destructive effect.

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?

It explains the targeting modes (listed contacts, one company, audience filters) and clarifies that already-messaged contacts stay. It also gives repeat guidance by saying to repeat while removed is above zero, though it does not explicitly contrast this with siblings such as removePendingCampaignContact.

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

All Leadpoet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?