Skip to main content
Glama

yuque_move_document

Move documents or table of contents nodes within Yuque knowledge bases by specifying source and target UUIDs to reorganize content hierarchies.

Instructions

Move a doc or TOC node to another parent by UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docIdNoDoc ID. Used to resolve nodeUuid if nodeUuid is omitted.
nodeUuidNoExisting TOC node UUID.
repoIdNoYuque repository ID.
repoNamespaceNoYuque repository namespace.
parentUuidNoTarget parent UUID.
targetUuidNoAlias of parentUuid.
actionModeNoTOC action mode.
positionNoInsert position.

Implementation Reference

  • Handler function for yuque_move_document tool.
    yuque_move_document: async (args, client) => jsonText(await client.moveDocument(args)),
  • Schema definition for yuque_move_document tool.
      name: "yuque_move_document",
      description: "Move a doc or TOC node to another parent by UUID.",
      inputSchema: {
        type: "object",
        properties: {
          docId: schemaProperty("number", "Doc ID. Used to resolve nodeUuid if nodeUuid is omitted."),
          nodeUuid: schemaProperty("string", "Existing TOC node UUID."),
          ...repoRefSchema(),
          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"] })
        }
      }
    },
Behavior2/5

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

No annotations provided, so description must carry full burden. It fails to disclose behavioral details: what happens to the original location (is it removed or copied?), implications of actionMode 'child' vs 'sibling', or whether the operation is atomic/reversible. Only mentions UUIDs are used.

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?

Single sentence, front-loaded with verb 'Move'. No redundant words. Efficiently conveys core operation without extraneous information.

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?

Adequate for identifying the tool's function, but incomplete given complexity: no mention of return values (no output schema), silent on parameter interdependencies (docId resolves nodeUuid), and omits behavioral implications of position and actionMode enums.

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 coverage is 100% with all 8 parameters documented. Description provides baseline context mapping 'doc' to docId and 'TOC node' to nodeUuid, but adds no syntax details, valid formats, or explanations of the parentUuid/targetUuid alias relationship 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?

States specific action 'Move' and resources 'doc or TOC node' with destination 'another parent'. Distinguishes from siblings like create_doc or delete_toc_node by focusing on relocation, though doesn't explicitly clarify difference from update_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?

Provides no guidance on when to use this tool versus alternatives like update_toc or update_repository_toc. Does not mention prerequisites (e.g., needing UUIDs from get_toc) or the relationship between docId and nodeUuid parameters (mutual exclusivity).

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