docmost-mcp-local

Overview Schema Source Related Servers Discussions Admin

create_page

Create a new page in a Docmost space by providing a title and optional Markdown content. Optionally set a parent page to nest it under.

Instructions

Create a new Docmost page in a space from Markdown content.

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

Input Schema

Name	Required	Description
`title`	Yes	Page title.
`markdown`	No	Page body as Markdown; converted to ProseMirror JSON before sending.
`space_id`	Yes	The Docmost space ID (UUID) to create the page in.
`parent_page_id`	No	Optional parent page ID to nest this page under (must be in the same space).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds the conversion detail ('converted to ProseMirror JSON') but does not disclose other behavioral traits like rate limits, authentication needs, or side effects. No contradiction with 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?

Single 11-word sentence. No fluff, every word earns its place. Front-loaded with the action and resource.

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

Completeness2/5

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

No output schema exists, so the description should explain return values or what happens after creation. It does not. Also omits mention of required prerequisites (e.g., space must exist). For a creation tool with 4 parameters, this is incomplete.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The description's 'from Markdown content' loosely relates to the markdown parameter but adds no meaningful information beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 verb 'create', the resource 'Docmost page', and the context 'in a space from Markdown content'. This distinguishes it from sibling tools like 'duplicate_page' (copy existing) and 'update_page' (modify existing).

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 when to use (creating a new page) but provides no explicit guidance on when not to use or alternatives. With 19 sibling tools, more exclusions or comparisons would help, but the context is clear enough for basic use.

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