flowforge-mcp

flowforge_remove_campaign_leads

DestructiveIdempotent

Bulk soft-delete a campaign's leads, optionally filtered by status, with a dry-run preview until confirm=true; pause the campaign first.

Instructions

Bulk soft-delete a campaign's leads, optionally only those in given statuses. Dry run until confirm=true; pause/stop the campaign first.

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": "flowforge_remove_campaign_leads"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context: the operation is a *soft* delete (implying recoverability), it is a no-op dry run by default, and the campaign must be stopped first. It does not say how long soft-deleted leads are retained or what happens to leads mid-call.

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 sentences, zero filler, with the destructive operation and its scoping stated first and the safety prerequisites immediately after. Every clause carries information an agent must have before calling.

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?

An output schema exists, so return values need not be explained, and the description covers the destructive nature, dry-run default and precondition. The only real gap is the absence of recovery guidance for a soft delete, which matters for a destructiveHint=true tool but is a minor omission given the annotation coverage.

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?

Although the aggregate coverage signal reports 0%, the schema itself carries dense per-property descriptions, so the baseline would already be 3. The description still adds meaning by framing confirm as a dry-run switch rather than a plain boolean and by flagging the status filter as an optional narrowing. It does not restate the 400 refusal for running campaigns, which lives only in the schema.

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?

States a specific verb and resource: bulk soft-delete of a campaign's leads, with the optional status scoping called out up front. This clearly separates it from flowforge_add_campaign_leads and flowforge_delete_campaign without needing to open 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 an explicit precondition ("pause/stop the campaign first") and explains the dry-run gate ("Dry run until confirm=true"), which is exactly the operational sequencing an agent needs. It stops short of naming sibling alternatives for removing leads or a whole campaign, so it is clear context rather than full when/when-not routing.

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

Deploy Server