yuque-mcp-plus

yuque_create_toc_node

Add title or link nodes to Yuque repository table of contents by specifying parent nodes, position, and type for organizing knowledge base structure.

Instructions

Create a TITLE or LINK node in the repository TOC tree.

Input Schema

TableJSON Schema

Name	Required	Description
`repoId`	No	Yuque repository ID.
`repoNamespace`	No	Yuque repository namespace.
`title`	Yes	Node title.
`nodeType`	No	Node type.
`url`	No	Optional URL when nodeType is LINK.
`parentUuid`	No	Target parent UUID.
`targetUuid`	No	Alias of parentUuid.
`actionMode`	No	TOC action mode.
`position`	No	Insert position.

Implementation Reference

src/tools.js:445-445 (handler)
The handler for 'yuque_create_toc_node' which calls client.createTocNode(args).
```
yuque_create_toc_node: async (args, client) => jsonText(await client.createTocNode(args)),
```

src/tools.js:213-230 (registration)

The schema and registration definition for 'yuque_create_toc_node'.

{
  name: "yuque_create_toc_node",
  description: "Create a TITLE or LINK node in the repository TOC tree.",
  inputSchema: {
    type: "object",
    properties: {
      ...repoRefSchema(),
      title: schemaProperty("string", "Node title.", { minLength: 1 }),
      nodeType: schemaProperty("string", "Node type.", { enum: ["TITLE", "LINK"] }),
      url: schemaProperty("string", "Optional URL when nodeType is LINK."),
      parentUuid: schemaProperty("string", "Target parent UUID."),
      targetUuid: schemaProperty("string", "Alias of parentUuid."),
      actionMode: schemaProperty("string", "TOC action mode.", { enum: ["child", "sibling"] }),
      position: schemaProperty("string", "Insert position.", { enum: ["append", "prepend"] })
    },
    required: ["title"]
  }
},

Tool Definition Quality

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure but offers minimal detail. It fails to explain the hierarchical manipulation behavior (child vs sibling, append vs prepend), does not clarify that targetUuid is an alias for parentUuid, and omits mutation consequences such as whether the operation is atomic or how it affects document visibility.

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 single sentence is efficient and contains no redundant words. It front-loads the action (Create) and specifies the resource types immediately, making it easy to parse.

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?

For a 9-parameter mutation tool involving complex hierarchical positioning (parent/sibling relationships, append/prepend logic), the description is inadequate. It lacks explanation of the tree structure mechanics, positioning behavior, and the alias relationship between targetUuid and parentUuid that is critical for correct invocation.

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?

With 100% schema description coverage, the baseline is 3. The description reinforces the nodeType enum values (TITLE/LINK) providing semantic context beyond the schema's generic 'Node type' label. However, it does not compensate for vague schema descriptions like 'TOC action mode' or explain the UUID relationships.

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 clearly states the verb (Create), the resource (TITLE or LINK node), and the location (repository TOC tree). It effectively distinguishes from siblings like yuque_create_doc and yuque_create_repo by specifying 'TOC tree'. However, it does not differentiate from yuque_update_repository_toc or yuque_update_toc, leaving potential ambiguity about when to create vs update.

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 like yuque_update_toc. It does not explain when to choose TITLE versus LINK types, nor does it mention prerequisites such as requiring either repoId or repoNamespace.

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

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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