docmost-mcp-local

by wisflux

Overview Schema Source Related Servers Discussions Admin

Rust

Local

update_page

Destructive

Update an existing Docmost page's title and/or Markdown content.

Instructions

Update an existing Docmost page's title and/or 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": {
      "page_id": "<page_id>"
    },
    "name": "update_page"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional new page title. Omit to leave the title unchanged.
`page_id`	Yes	The Docmost page ID or slug ID to update.
`markdown`	No	Optional new page body as Markdown; replaces the existing content. Omit to leave content unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds minimal extra behavioral context beyond the parameter descriptions in the schema. It does not disclose side effects, authentication needs, or rate limits, but the core safety profile is covered by 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?

The description is a single, front-loaded sentence with no wasted words. Every word contributes to the purpose, making it highly concise and well-structured.

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 update tool with no output schema, the description covers the essential purpose and constraints. It could mention the return value (e.g., the updated page) but the tool's behavior is clear enough for an agent to understand and invoke correctly.

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%, with all three parameters clearly described in the schema. The tool description does not add new meaning beyond what is already stated in the parameter descriptions, achieving the baseline score.

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 'update', the resource 'existing Docmost page', and the specific fields that can be updated (title and/or Markdown content). It effectively distinguishes this tool from siblings such as create_page, copy_page_to_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 Guidelines4/5

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

The description implies that the tool should be used only for existing pages ('update an existing...'). It provides clear context for when to use, but does not explicitly mention when not to use or compare with alternatives like create_page for new pages.

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