Skip to main content
Glama
Sign In
feishu-user-plugin

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

move_wiki_node

Move a Wiki node to a different parent within the same space or to a different space. Specify the source space and node token, with optional new parent or target space.

Instructions

[Official API] Move a Wiki node to a different parent (within the same space) or to a different space. Pass at least one of target_parent_token / target_space_id.

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": {
      "space_id": "<space_id>",
      "node_token": "<node_token>"
    },
    "name": "move_wiki_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYesSource space ID
node_tokenYesWiki node token to move
target_parent_tokenNoNew parent wiki node token (optional)
target_space_idNoNew target space ID (optional; same-space move if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It accurately describes the core behavior (moving a node) and adds the parameter constraint. However, it does not disclose potential side effects such as impact on child nodes, permission changes, or reversibility. With no annotations, this is a moderate level of transparency.

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 two concise sentences with the key information front-loaded ('Move a Wiki node'). Every sentence provides necessary context without redundancy, making it highly efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a move operation with four parameters and no output schema, the description covers the essential use case, including the required parameter condition and the two move scenarios. It lacks deeper behavioral context (e.g., permissions, effects on children) but given the moderate complexity, it is reasonably complete.

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 schema already provides descriptions for all 4 parameters (100% coverage). The description adds valuable semantic context beyond the schema by explicitly stating that at least one of the two optional parameters must be provided, clarifying the relationship between target_parent_token and target_space_id. This improves the agent's ability to invoke the tool correctly.

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 action ('Move a Wiki node') and specifies the two possible scopes: to a different parent within the same space or to a different space. This distinguishes it from sibling tools like copy_wiki_node or update_wiki_node, which have different purposes.

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

Usage Guidelines4/5

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

The description explicitly instructs that at least one of target_parent_token or target_space_id must be passed, giving clear usage guidance. It also defines the two move scenarios, but does not explicitly mention when not to use this tool or point to alternatives, so it falls short of a 5.

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

Deploy Server

Other Tools