docmost-mcp

Create a Docmost page

create_page

Creates a page from Markdown at a space root or under a parent page, then returns its URL.

Instructions

Creates a page from Markdown at the root of a space or under a parent page, and returns its URL.

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

Input Schema

Name	Required	Description
`icon`	No	Optional emoji shown next to the title.
`title`	Yes	Page title.
`spaceId`	No	Space id from list_spaces; optional when parentPageId is given.
`markdown`	Yes	Page body in Markdown; do not repeat the title as a leading # heading.
`parentPageId`	No	Create the page under this page instead of at the space root.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

B3.4/5.0

Behavior3/5

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

There are no annotations, so the description carries the full behavioral burden. It discloses that the operation returns the new page's URL, which is genuinely useful with no output schema, but it omits permission requirements, error/failure behavior, and any title-collision constraints for a mutation operation.

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 zero filler; the action, the two source locations, and the return value are all packed into one clause chain with no redundant restatement of the name.

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 5-parameter create tool with no annotations and no output schema, the description covers the essential invocation facts and uniquely supplies the return value. It would be complete with a hint about required permissions or the spaceId/parentPageId dependency, but nothing critical for calling it is missing.

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 the schema already documents icon, title, spaceId, markdown and parentPageId with placement semantics. The description only echoes 'from Markdown' and adds no syntax, format, or size guidance beyond the schema, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Creates a page from Markdown') and specifies the two placement modes (space root or under a parent page). The create verb inherently separates it from update_page/get_page/list_pages, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like update_page, and no prerequisites (e.g. needing a valid spaceId from list_spaces) are stated. Placement context is only implicit, and the agent is left to infer conditions entirely.

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

Deploy Server