flowforge-mcp

flowforge_delete_campaign

DestructiveIdempotent

Permanently deletes a campaign by ID, returning confirmation on success or an error if not found. Use it to remove campaigns that should no longer exist; deletion cannot be undone.

Instructions

Permanently delete a campaign. This cannot be undone.

Args: params: campaign_id to delete.

Returns: A confirmation message on success.

Error Handling: Returns "Error: Resource not found..." if the ID is wrong.

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_delete_campaign"
  }
}

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

A3.5/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 openWorldHint=true, so the description's "cannot be undone" is partially redundant. It nevertheless adds real behavioral detail beyond the annotations: the success return value (a confirmation message) and the specific error string returned for a bad ID.

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?

The irreversible action is front-loaded in the first sentence, followed by compact Args/Returns/Error sections. The docstring scaffolding is slightly heavier than needed for a single-parameter tool but contains no filler prose.

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?

With an output schema present, the description need not explain return shape, yet it does summarize success and the not-found error path, which is useful. The notable gap is cascade behavior — it never says whether leads, calls, or settings attached to the campaign are also removed, which matters for a destructive operation.

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% and the top-level schema has a non-obvious "params" wrapper, which the Args section does clarify by naming the inner campaign_id field. Beyond that, the description only restates "campaign_id to delete" and adds no format, source, or example detail (e.g., where to obtain the ID).

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?

"Permanently delete a campaign" gives a specific verb and resource, and the permanence qualifier sharpens the intent. It does not, however, distinguish itself from adjacent siblings such as flowforge_control_campaign or flowforge_update_campaign_settings, which an agent might reasonably confuse with removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g., use control_campaign to pause rather than delete). The warning "This cannot be undone" is a caution, not a routing rule, so the agent must infer the conditions for calling this tool.

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

Deploy Server