WorkFlowy MCP Server

workflowy_update_node

Modify existing WorkFlowy nodes by updating their name, note content, layout style, or completion status using the node's unique identifier.

Instructions

Update an existing WorkFlowy node

Input Schema

TableJSON Schema

Name	Required	Description	Default
`node_id`	Yes
`name`	No
`note`	No
`layout_mode`	No
`_completed`	No

Output Schema

TableJSON Schema

Name	Required	Description
`ch`	No	Child nodes
`cp`	No	Completion status (for tests)
`id`	Yes	Unique identifier for the node
`data`	No	Node data including layoutMode
`name`	No	Text content of the node
`note`	No	Note content attached to the node
`parentId`	No	Parent node ID
`priority`	No	Sort order
`createdAt`	No	Creation timestamp (Unix timestamp)
`modifiedAt`	No	Last modification timestamp
`completedAt`	No	Completion timestamp (null if not completed)

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv1.0.0Jan 3, 2026

addedOutput schema / description

Added value: +"Represents a single node in the WorkFlowy outline hierarchy."

addedOutput schema / example

Added value: +{
+  "children": [],
+  "completedAt": null,
+  "createdAt": 1704067200,
+  "id": "node-123",
+  "layoutMode": "bullets",
+  "modifiedAt": 1704067200,
+  "name": "Example Node",
+  "note": "This is a note",
+  "priority": 1
+}

addedOutput schema / properties / ch

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/WorkFlowyNode"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Child nodes"
+}

addedOutput schema / properties / completedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Completion timestamp (null if not completed)"
+}

addedOutput schema / properties / cp

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Completion status (for tests)"
+}

addedOutput schema / properties / createdAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Creation timestamp (Unix timestamp)"
+}

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Node data including layoutMode"
+}

addedOutput schema / properties / id

Added value: +{
+  "description": "Unique identifier for the node",
+  "type": "string"
+}

addedOutput schema / properties / modifiedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Last modification timestamp"
+}

addedOutput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Text content of the node"
+}

addedOutput schema / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Note content attached to the node"
+}

addedOutput schema / properties / parentId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Parent node ID"
+}

addedOutput schema / properties / priority

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sort order"
+}

removedOutput schema / properties / result

Removed value: -{
-  "$ref": "#/$defs/WorkFlowyNode"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "id"
+]

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedNov 9, 2025

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't specify whether this requires authentication, what happens when only some fields are provided (partial updates), whether changes are reversible, or what the response looks like. For a mutation tool with 5 parameters and no annotation coverage, this is a significant gap in behavioral context.

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 at just 5 words, with zero wasted language. It's front-loaded with the essential action and resource. While it's arguably too brief given the tool's complexity, it achieves maximum efficiency within its limited scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters with 0% schema coverage, no annotations, and involves mutation operations, the description is severely incomplete. While an output schema exists (which helps with return values), the description doesn't address key contextual aspects like authentication requirements, error conditions, partial update behavior, or relationships with sibling tools. For a node update operation in a hierarchy system, this leaves too many unknowns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description mentions no parameters at all, failing to compensate for this complete lack of schema documentation. Users must guess what 'node_id', 'name', 'note', 'layout_mode', and '_completed' mean based solely on their names, which is insufficient for proper tool invocation.

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?

The description clearly states the verb ('Update') and resource ('an existing WorkFlowy node'), making the purpose unambiguous. It distinguishes this from sibling tools like 'create_node' and 'delete_node' by specifying it's for existing nodes. However, it doesn't specify what aspects can be updated (name, note, layout_mode, completion status), which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'update_node' over 'complete_node' or 'uncomplete_node' for completion status changes, or how it relates to 'get_node' for retrieving node data before updating. There's no context about prerequisites or typical use cases.

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

Deploy Server