Skip to main content
Glama
Sign In
docmost-community-mcp

docmost-community-mcp

by dilruwanm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_page

Creates a wiki page in a specified space from Markdown content, with optional icon and parent page for hierarchical organization.

Instructions

Create a page in a space. Body is Markdown and is persisted in place (Docmost v0.71+). Can nest under a parent.

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

NameRequiredDescriptionDefault
iconNoPage icon, usually an emoji
titleYesPage title
markdownNoPage body as Markdown
space_idYesSpace UUID or slug
parent_page_idNoParent page UUID to nest under

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The description goes beyond the annotations by disclosing that the body is Markdown, is persisted 'in place', and notes a version dependency (Docmost v0.71+). This is useful behavioral context that the readOnly/destructive hints do not cover. 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?

Two short, information-dense sentences with no fluff. The primary action is front-loaded, followed by the two most behaviorally relevant details: Markdown persistence and parent nesting.

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?

Given the annotations and schema, the description covers the important aspects of creating a page. It does not mention return values or error cases, but no output schema exists and the tool is relatively simple. The version note and nesting detail make it sufficiently complete for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by clarifying that markdown is the body format and that parent_page_id enables nesting under a parent. It does not deeply explain icon/title semantics, but the schema already documents those adequately.

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 action ('Create a page'), the resource ('in a space'), and adds distinguishing details: Markdown body, persistence behavior, and optional parent nesting. This separates it from sibling tools like create_space or create_comment without requiring schema inspection.

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?

The purpose is self-evident: use this to create a new page in a space, optionally under a parent. It provides clear context for when to invoke it, though it does not explicitly name alternatives or exclusions (e.g., update_page for modifying existing pages).

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

Deploy Server

Other Tools