docmost-community-mcp

Overview Schema Source Related Servers Discussions Admin

move_page_to_space

Relocate a page along with its accessible sub-pages to a target space. Provide the page ID and destination space to reorganize your wiki.

Instructions

Move a page and its accessible sub-pages to a different space.

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": {
      "page_id": "<page_id>",
      "space_id": "<space_id>"
    },
    "name": "move_page_to_space"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	Page UUID or slugId
`space_id`	Yes	Destination space

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already communicate that the operation is a mutation and not flagged destructive; the description adds a meaningful behavioral nuance by stating that only 'accessible' sub-pages are moved, which is not present in the schema or annotations. It does not discuss permission requirements or return behavior, but with annotations covering the safety profile this is acceptable.

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?

A single, front-loaded sentence with no filler. Every word carries meaning: the action, the scope (page and accessible sub-pages), and the destination (different space).

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 two-parameter move operation, the core call parameters and scope are covered, and the accessible-sub-pages caveat is important. The only notable gap is that with no output schema the description does not state expected return values or error conditions, but this does not block 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?

Schema coverage is 100% and both parameters already have descriptions ('Page UUID or slugId' and 'Destination space'), so the baseline applies. The description adds no new parameter-level detail beyond reinforcing that the destination is a space.

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 uses a specific verb ('Move') with a specific resource ('a page and its accessible sub-pages') and destination ('to a different space'). It clearly distinguishes this from copy_page_to_space and from move_page by emphasizing the cross-space destination and the sub-page scope.

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?

The phrase 'to a different space' gives implied context for when this tool is appropriate, but there is no explicit when-to-use/when-not-to-use guidance and no reference to alternatives such as move_page or copy_page_to_space. An agent must infer the routing from sibling names.

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