Delete Workflow Edge

Destructive Removes a single connection between two nodes, and clears the matching entry from the source node’s routing config (config.outputs/config.output) so it can’t keep silently routing to a node with no structural edge behind it. This is NOT reversible, though re-adding it with add_workflow_edge is straightforward if needed. Edges FROM a CONDITIONAL/TIME/APPLICATION node cannot be deleted outright — those node types always require every route to be set (validateNodeConfig rejects clearing it), so removing one would leave the node in a state it can never be saved in again. Use add_workflow_edge with a different to_node_id to REPLACE where such a route points instead.

Parameters

Name	Type	Required	Description
`workflow_id`	`string`	Yes	The workflow ID, e.g. workflow_abc123
`edge_id`	`string`	Yes	The edge ID, e.g. edge_abc123 — from get_workflow_structure

Complete input schema

{
  "type": "object",
  "properties": {
    "workflow_id": {
      "type": "string",
      "description": "The workflow ID, e.g. workflow_abc123"
    },
    "edge_id": {
      "type": "string",
      "description": "The edge ID, e.g. edge_abc123 — from get_workflow_structure"
    }
  },
  "required": [
    "workflow_id",
    "edge_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Registered output schema

{
  "type": "object",
  "properties": {
    "deleted": {
      "type": "boolean",
      "description": "True when the edge was deleted"
    },
    "edge_id": {
      "type": "string",
      "description": "The deleted edge ID, as provided"
    }
  },
  "required": [
    "deleted",
    "edge_id"
  ],
  "additionalProperties": true,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Before you call

Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
Provide the required parameters: workflow_id, edge_id.
Confirm the exact target and intended effect with the user before calling.

Example MCP request

Send tools/call after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_workflow_edge",
    "arguments": {
      "workflow_id": "workflow_abc123",
      "edge_id": "edge_abc123"
    }
  }
}

Successful results include structuredContent and a text content block containing the same JSON. Check isError first, then read structuredContent or parse content[0].text. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Confirm the response is not marked isError. Call Get Workflow Structure to read the affected resource. Verify that the target is removed or disconnected before reporting completion.

Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

Get Workflow Structure: get_workflow_structure
Add Workflow Edge: add_workflow_edge
List Workflows: list_workflows
Get Workflow: get_workflow

Start Here

Tool Reference

Parameters

Complete input schema

Registered output schema

Before you call

Example MCP request

Verify the result

Retry safety

​Parameters

​Complete input schema

​Registered output schema

​Before you call

​Example MCP request

​Verify the result

​Retry safety

​Related MCP tools

​Related guides

Parameters

Complete input schema

Registered output schema

Before you call

Example MCP request

Verify the result

Retry safety

Related MCP tools

Related guides