Workflowy MCP Server

workflowy_list_nodes

Retrieve child nodes under a specified parent node in your Workflowy outline. If no parent ID is provided, returns root-level nodes.

Instructions

List child nodes under a parent node. If no parentId is provided, lists root-level nodes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workflowy_list_nodes"
  }
}

Input Schema

Name	Required	Description	Default
`parentId`	No	ID of the parent node (optional, defaults to root)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The description implies a read-only operation by using 'list', but with no annotations provided, it should more clearly state that it only reads and does not modify data. It also omits details about whether the listing is paginated, ordered, or includes full node data.

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 only two sentences, front-loading the core action and then clarifying the default behavior. Every word serves a purpose with no redundancy or unnecessary detail.

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

Completeness3/5

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

For a simple list tool with no output schema, the description covers the core functionality but lacks details about the output format (e.g., what fields are returned for each node, whether it's recursive). Given no output schema, more context about the return value would be helpful.

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?

The input schema already describes parentId, but the description adds crucial context: 'If no parentId is provided, lists root-level nodes.' This clarifies the default behavior, which is not fully captured by the schema's 'optional, defaults to root' alone.

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 'List child nodes under a parent node' with a specific verb and resource. It distinguishes itself from siblings like workflowy_get_node (which gets a single node) and workflowy_get_node_hierarchy (which returns full hierarchy), by focusing on listing children or root nodes.

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 provides basic guidance on when to provide parentId, but does not explicitly mention when not to use this tool or offer alternatives among the many siblings. For example, it does not suggest workflowy_get_node for retrieving a single node or workflowy_search for querying by criteria.

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

Deploy Server