cognigy-ai-mcp-management-server

delete_node

DestructiveIdempotent

Permanently delete a node from a Cognigy.AI flow. Use dry run to validate the operation before irreversible deletion.

Instructions

Deletes a node from a Cognigy.AI flow. MUTATING & DESTRUCTIVE: This permanently removes the node. Use dryRun=true (default) to validate first. Child nodes may also be affected.

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": {
      "flowId": "<flowId>",
      "nodeId": "<nodeId>"
    },
    "name": "delete_node"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true (default), validates the operation without deleting. Set to false to actually delete. WARNING: Deletion cannot be undone via API.
`flowId`	Yes	The flow ID containing the node to delete
`nodeId`	Yes	The ID of the node to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds value beyond annotations by stating the permanent nature of deletion, the default dryRun behavior, and potential side effects on child nodes. Annotations already indicate destructiveHint=true and idempotentHint=true, but the description elaborates on the practical implications.

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 extremely concise with two sentences that cover purpose, destructiveness, usage guideline, and side effects. No wasted words; every sentence earns its place.

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 delete operation with three well-documented parameters and no output schema, the description is fully complete. It covers the action, safety validation, permanence, and child node impact, leaving no ambiguity for an AI agent.

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 100% with descriptions for all parameters. The description enhances this by emphasizing the dryRun parameter's role in validation and the permanent delete warning, adding context beyond 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?

The description clearly states the action ('Deletes a node') and the resource ('from a Cognigy.AI flow'). It is specific and distinguishes itself from sibling tools like create_node, update_node, and move_node.

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?

Provides explicit guidance to use dryRun=true for validation before actual deletion and warns that child nodes may be affected. However, it does not explicitly mention when not to use this tool versus alternatives, though deletion is a unique operation.

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

Deploy Server