Skip to main content
Glama

workflowy_delete_node

Remove a WorkFlowy outline node and its nested content from your task management system using its unique identifier.

Instructions

Delete a WorkFlowy node and all its children

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler function for 'workflowy_delete_node'. Delegates to WorkFlowyClient.delete_node with rate limiting and error handling.
    @mcp.tool(name="workflowy_delete_node", description="Delete a WorkFlowy node and all its children")
    async def delete_node(node_id: str) -> dict:
        """Delete a WorkFlowy node and all its children.
    
        Args:
            node_id: The ID of the node to delete
    
        Returns:
            Dictionary with success status
        """
        client = get_client()
    
        if _rate_limiter:
            await _rate_limiter.acquire()
    
        try:
            success = await client.delete_node(node_id)
            if _rate_limiter:
                _rate_limiter.on_success()
            return {"success": success, "deleted_id": node_id}
        except Exception as e:
            if _rate_limiter and hasattr(e, "__class__") and e.__class__.__name__ == "RateLimitError":
                _rate_limiter.on_rate_limit(getattr(e, "retry_after", None))
            raise
  • Core implementation in WorkFlowyClient that performs the HTTP DELETE request to the WorkFlowy API endpoint /nodes/{node_id} and handles responses/errors.
    async def delete_node(self, node_id: str) -> bool:
        """Delete a node and all its children."""
        try:
            response = await self.client.delete(f"/nodes/{node_id}")
            # Delete endpoint returns just a message, not nested data
            await self._handle_response(response)
            return True
        except httpx.TimeoutException as err:
            raise TimeoutError("delete_node") from err
        except httpx.NetworkError as e:
            raise NetworkError(f"Network error: {str(e)}") from e
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. It states the tool deletes a node and its children, implying a destructive mutation, but lacks details on permissions needed, irreversibility, error conditions, or rate limits, leaving significant gaps for a deletion 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?

The description is a single, efficient sentence that front-loads the core action ('Delete') and resource, with zero wasted words. It's appropriately sized for a simple tool with one parameter.

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?

Given the tool's destructive nature and lack of annotations, the description is minimally adequate but incomplete. It specifies what the tool does but omits critical behavioral context (e.g., permanence, errors). The presence of an output schema helps, but more guidance is needed for safe use.

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 description doesn't add specific details about the 'node_id' parameter beyond what the schema implies (a string identifier). However, with only one parameter and 0% schema description coverage, the description's clarity about the tool's purpose provides adequate context, compensating for the minimal parameter documentation.

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 the specific action ('Delete') and resource ('a WorkFlowy node and all its children'), distinguishing it from siblings like workflowy_update_node or workflowy_get_node by focusing on permanent removal rather than modification or retrieval.

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 explicit guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., node must exist), exclusions (e.g., cannot delete root nodes), or compare to siblings like workflowy_uncomplete_node for different deletion scenarios.

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/vladzima/workflowy-mcp'

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