Get Workflow Structure

Read only Returns all nodes and edges currently in a workflow’s graph — use this to see the current build state before deciding what to add next, to find node ids to connect with add_workflow_edge, and as a final self-check before activating (confirm exactly one node has no incoming edge, every other node has at least one, and a CONVERTED and DROPPED node both exist and are connected).

Parameters

Name	Type	Required	Description
`workflow_id`	`string`	Yes	The workflow ID, e.g. workflow_abc123

Complete input schema

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

Registered output schema

{
  "type": "object",
  "properties": {
    "nodes": {
      "type": "array",
      "description": "All nodes in the workflow graph, each with a prefixed node_ id, node_type, label, and config"
    },
    "edges": {
      "type": "array",
      "description": "All directed edges in the workflow graph, each with prefixed edge_/node_ ids and an optional label"
    }
  },
  "required": [
    "nodes",
    "edges"
  ],
  "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.

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": "get_workflow_structure",
    "arguments": {
      "workflow_id": "workflow_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, parse content[0].text as JSON, and verify that returned IDs and workspace data match the request.

Retry safety

This tool does not change workspace data. Retrying after a transient transport failure is safe.

Add Workflow Edge: add_workflow_edge

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