Skip to main content
Glama

yuque_delete_toc_node

Remove a title or link node from a Yuque repository's table of contents tree to manage document structure and hierarchy.

Instructions

Delete a TITLE or LINK node from the repository TOC tree.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoIdNoYuque repository ID.
repoNamespaceNoYuque repository namespace.
nodeUuidYesExisting TOC node UUID.
parentUuidNoOptional parent TOC UUID. If omitted, the server resolves the delete strategy from the TOC tree.
targetUuidNoAlias of parentUuid.
actionModeNoOptional TOC action mode override.

Implementation Reference

  • The handler implementation for yuque_delete_toc_node, which delegates to the client.deleteTocNode method.
    yuque_delete_toc_node: async (args, client) => jsonText(await client.deleteTocNode(args)),
  • The input schema definition for the yuque_delete_toc_node tool.
    name: "yuque_delete_toc_node",
    description: "Delete a TITLE or LINK node from the repository TOC tree.",
    inputSchema: {
      type: "object",
      properties: {
        ...repoRefSchema(),
        nodeUuid: schemaProperty("string", "Existing TOC node UUID."),
        parentUuid: schemaProperty("string", "Optional parent TOC UUID. If omitted, the server resolves the delete strategy from the TOC tree."),
        targetUuid: schemaProperty("string", "Alias of parentUuid."),
        actionMode: schemaProperty("string", "Optional TOC action mode override.", { enum: ["child", "sibling"] })
      },
      required: ["nodeUuid"]
    }
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 but only states the basic deletion action. It fails to disclose whether deletion is permanent, how the server resolves the delete strategy when parentUuid is omitted (mentioned only in the schema), or whether child nodes are affected.

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 with zero redundancy. Every word earns its place by conveying the action, target type, and location context upfront.

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 the tool's moderate complexity (6 parameters with interdependencies like targetUuid being an alias of parentUuid, an enum for actionMode, and a destructive operation), the single-sentence description is insufficient. It lacks explanation of output behavior and the semantic distinctions between optional parameter combinations.

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%, establishing a baseline of 3. The description mentions 'TITLE or LINK' node types, which adds semantic context not explicitly constrained in the schema, but does not elaborate on the relationship between repoId/repoNamespace or clarify the alias relationship between parentUuid and targetUuid mentioned in 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?

The description uses a specific verb ('Delete') and clearly identifies the resource ('TITLE or LINK node from the repository TOC tree'), which distinguishes it from sibling tools like yuque_delete_doc or yuque_delete_repo. However, it lacks context on what distinguishes TITLE from LINK nodes or when to prefer this over yuque_update_repository_toc.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., yuque_update_repository_toc), nor does it mention prerequisites such as requiring either repoId or repoNamespace to identify the target repository.

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/MichealJou/yuque-mcp-plus'

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