docmost-mcp-local

by wisflux

Overview Schema Source Related Servers Discussions Admin

Rust

Local

duplicate_page

Duplicate a Docmost page and its sub-pages within its space by specifying the page ID.

Instructions

Duplicate a Docmost page (with its sub-pages) within its 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>"
    },
    "name": "duplicate_page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	The Docmost page ID or slug ID to duplicate within its space.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare destructiveHint=false and readOnlyHint=false, indicating a mutation but not destructive. Description adds that sub-pages are included, but omits details like duplicate naming conventions, permission inheritance, or return value.

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 the key information. Every word is meaningful, no wasted text.

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 simple tool with one parameter and no output schema, the description covers the basic functionality. However, it lacks information about the return value (e.g., success indicator or new page ID).

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% for the single parameter page_id. The description repeats 'within its space' which is already in the schema, adding no new semantic 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?

Description clearly states the action (Duplicate), the resource (Docmost page), and scope (with sub-pages within its space). This distinguishes it from sibling tools like copy_page_to_space (which copies to another space) and move_page.

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 description implies usage for duplicating a page in the same space but does not explicitly state when to use this tool versus alternatives like copy_page_to_space or move_page.

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