Skip to main content
Glama

yuque_web_batch_move_catalog_nodes

Moves multiple document nodes under a target catalog node in Yuque, including cross-repository moves, using a single batch request from a source knowledge base.

Instructions

Cookie-based: Batch move document nodes to a target catalog node. PUT /api/catalog_nodes/batch. Supports cross-repo move (target_book_id may differ from book_id). No membership required. Moves the specified node_uuids under the target_uuid directory as children. 详见 references/api/web_doc_api.md

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_uuids": "<node_uuids>",
      "target_uuid": "<target_uuid>",
      "book_id": "<book_id>"
    },
    "name": "yuque_web_batch_move_catalog_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes源知识库 ID(数字,必填)。节点当前所在的知识库。 / Source repository ID (numeric, required). The repo the nodes currently live in.
node_uuidsYesNode UUIDs to move, as a string array or JSON-encoded string (required)
target_uuidYesTarget catalog node UUID to move into (required)
target_book_idNo目标知识库 ID(数字,可选)。跨库移动时填目标知识库 ID。缺省为 book_id(同库移动)。 / Target repository ID (numeric, optional). For cross-repo move set this to the destination repo. Defaults to book_id (same-repo move).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.0.0
    • addedInput schema / properties / node_uuids / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / node_uuids / description
      Previous value: -"JSON array string of node UUIDs to move, e.g. '[\"uuid1\",\"uuid2\"]' (required)"New value: +"Node UUIDs to move, as a string array or JSON-encoded string (required)"
    • removedInput schema / properties / node_uuids / type
      Removed value: -"string"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: cookie-based auth, the PUT endpoint, cross-repo support, no membership requirement, and that moved nodes end up as children of target_uuid. It does not disclose permissions beyond membership, whether the move is atomic or partial on batch failure, or whether the source location is cleared.

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

Conciseness4/5

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

The scope statement and endpoint are front-loaded, and each sentence carries information (auth, endpoint, cross-repo, permissions, placement). The trailing reference to references/api/web_doc_api.md is the only element that adds length without inline value.

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?

For a 4-parameter batch mutation with no annotations and no output schema, the description covers auth, scope, and target placement adequately. It falls short on batch-specific behavior an agent needs: partial-failure semantics and any indication of what the response contains.

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%, so the schema itself documents all four parameters, including the book_id vs target_book_id relationship. The description restates the cross-repo/default behavior and the child-placement semantics of target_uuid, adding modest reinforcement rather than new meaning.

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+resource combination ('Batch move document nodes to a target catalog node') and names the underlying endpoint, so the operation is unambiguous. The word 'Batch' differentiates it from the singular yuque_web_move_catalog_node by scope, though the description never explicitly contrasts the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful ad-hoc context: cross-repo moves are allowed when target_book_id differs from book_id, and no membership is required. However, it never states when to prefer this tool over yuque_web_move_catalog_node (single node) or yuque_web_copy_catalog_node, leaving alternative selection to inference from names.

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