Workflowy MCP Server

workflowy_get_node_hierarchy

Retrieve a Workflowy node and its descendant hierarchy to view full outline context around a specific item.

Instructions

Get a node with its children and descendants to see the full context and structure around it. Useful after finding a node via search to understand where it lives in your outline.

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

Input Schema

Name	Required	Description	Default
`nodeId`	Yes	ID of the node to retrieve with its hierarchy
`depth`	No	How many levels of children to include (0 = just the node, 1 = node + direct children, 2 = node + children + grandchildren, etc.). Default: 1, Max: 5

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations exist, so the description fully relies on itself. It discloses that the tool retrieves the node, children, and descendants, and the depth parameter controls hierarchy levels. No side effects are mentioned, but it's a read operation.

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?

Two sentences: first defines purpose, second gives usage context. Every word is necessary; no fluff.

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

Completeness5/5

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

For a simple hierarchy retrieval tool with two well-defined parameters and no output schema, the description fully covers the needed information to use it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds no extra parameter details beyond what the schema provides, but the schema itself is clear.

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 'Get a node with its children and descendants', which is a specific verb and resource. It differentiates from sibling tools like workflowy_get_node and workflowy_search.

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

Usage Guidelines4/5

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

The description advises using this tool 'after finding a node via search to understand where it lives in your outline', providing clear context. It doesn't explicitly exclude other scenarios but implies its primary use case.

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

Deploy Server