Workflowy MCP Server

workflowy_create_node

Create a new bullet point node in Workflowy with optional parent, notes, priority, and display mode.

Instructions

Create a new node (bullet point) in Workflowy. Can specify parent node, content, notes, and display mode.

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": {
      "name": "<name>"
    },
    "name": "workflowy_create_node"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The main text content of the node (supports markdown)
`parentId`	No	ID of the parent node (optional, defaults to root)
`note`	No	Optional extended description/notes for the node
`priority`	No	Sort order among siblings (optional)
`layoutMode`	No	Display style for the node (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It notes that parentId defaults to root, but does not disclose behavior on invalid IDs, nesting limits, atomicity, authentication requirements, or response structure. This leaves significant behavioral gaps.

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 two concise sentences without any fluff. It front-loads the core purpose and immediately lists customizable options. Every phrase earns its place.

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?

Despite 5 parameters and no output schema, the description lacks details on error handling, prerequisites (e.g., parent node existence), or operational context (e.g., immediate visibility). This is insufficient for the tool's complexity.

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?

Schema description coverage is 100%, so the schema already documents parameters. The description merely restates 'parent node, content, notes, and display mode' without adding new meaning, such as constraints or formatting rules.

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 'Create a new node (bullet point) in Workflowy' with specific verb and resource, and mentions customizable fields (parent, content, notes, display mode). It distinguishes from sibling tools like update, delete, etc.

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

Usage Guidelines3/5

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

The description implies using this tool to add a new node, but does not explicitly state when to use it vs alternatives like workflowy_complete_node or workflowy_update_node. No exclusion criteria or context is provided.

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

Deploy Server