Skip to main content
Glama
Sign In
docmost-mcp

docmost-mcp

by punyamsingh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a Docmost page

update_page

Edit an existing Docmost wiki page: change its title or icon, or replace, append, or prepend Markdown body content.

Instructions

Replaces, appends to or prepends to a page body in Markdown, and can rename it or change its icon.

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": {
      "pageId": "<pageId>"
    },
    "name": "update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoNew emoji icon.
titleNoNew page title.
pageIdYesPage id, slug id, or the full page URL copied from the browser.
markdownNoNew Markdown content; omit to change only the title or icon.
operationNoHow markdown is applied to the existing body; defaults to replace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does communicate that the body can be overwritten (a destructive behavior) and that title/icon are optional modifications, but it says nothing about permissions, reversibility, versioning of overwritten content, or failure modes. The operation semantics it implies largely duplicate the schema enum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the primary action (body modification) and tacks on secondary capabilities. Efficient, with only mild redundancy against the schema's operation enumeration.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the main capabilities adequately but omits auth/permission requirements, confirmation of what is returned, and any warning about losing existing content on replace. It is minimally sufficient rather than complete.

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 coverage is 100%, so every parameter is already documented in the schema, including pageId accepting slug/URL, the operation enum, and the ability to omit markdown. The description adds no format or constraint detail beyond that baseline.

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?

Names a specific verb set (replaces, appends, prepends) and resource (page body), plus ancillary actions (rename, change icon). It is clearly an update tool and distinct from create_page/get_page by its mutating framing, 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?

The description says what can be changed but never states when to use this tool versus create_page or get_page, nor any prerequisites such as needing an existing pageId. Usage is only implied by the word 'update'.

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