Skip to main content
Glama

workflowy_get

Destructive

Retrieve a WorkFlowy node and its descendants by ID, with configurable recursion depth, ancestor inclusion, and access method (get/export/backup).

Instructions

Get node and descendants

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ancestor_depthNoInclude N levels of ancestors (-1 for all, 0 for none; requires export or backup method)
depthNoRecursion depth (-1 for all, default 2)
idNoID (default: root)None
include_ancestorsNoWrap result in ancestor path from root to target node (requires export or backup method)
include_empty_namesNoInclude items with empty names
methodNoAccess method: get, export, or backup (default: auto based on depth)
to_ancestorNoInclude ancestors up to and including this node ID (requires export or backup method)
Behavior1/5

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

Description says 'Get' (read-only), but annotations set destructiveHint=true, indicating a contradiction. No further behavioral details provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 4 words, but lacks necessary detail to fully inform an AI agent. It is front-loaded but under-specified.

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 7 parameters, many siblings, and no output schema, the description is incomplete. It relies entirely on schema descriptions, which may not capture all nuances.

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?

Input schema has 100% coverage with descriptions, so baseline is 3. Description adds no additional meaning beyond the schema.

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?

Description clearly states 'Get node and descendants', using a specific verb and resource. However, it does not differentiate from siblings like workflowy_list, which might also retrieve nodes.

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?

No guidance on when to use this tool vs alternatives. No exclusions or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mholzen/workflowy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server