docmost-mcp-local

by wisflux

Overview Schema Source Related Servers Discussions Admin

Rust

Local

move_page

Idempotent

Move a Docmost page to a new parent page or the space root, appending it after existing children.

Instructions

Move a Docmost page under a new parent page, or to the space root. The page is appended after the target parent's existing children.

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>"
    },
    "name": "move_page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	The Docmost page ID or slug ID to move.
`parent_page_id`	No	Optional new parent page ID within the same space. Omit to move the page to the space root. The page is appended after the parent's existing children.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. Description adds behavioral detail about ordering (appended after existing children) and scope (within same space). No contradictions, adds value beyond annotations.

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?

Two sentences, front-loaded with action and resource, then additional detail. Every word earns its place. No fluff.

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

Completeness5/5

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

Tool is simple with 2 params, no output schema, and annotations cover mutation and idempotency. Description covers the two use cases and ordering behavior completely. No missing critical information.

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 baseline is 3. Tool description doesn't add new parameter semantics beyond what schema already provides for both page_id and parent_page_id. No additional value.

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?

Clearly states the action (move) and resource (Docmost page), specifies two destinations (new parent page or space root), and distinguishes from sibling tools like copy_page_to_space and move_page_to_space by focusing on parent changes within the same space.

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?

Explicitly describes when to use: moving a page under a new parent or to space root. Implicitly excludes cross-space moves (use move_page_to_space), but lacks explicit alternative naming. Clear context for appropriate use.

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