docmost-mcp-local

by wisflux

Overview Schema Source Related Servers Discussions Admin

Rust

Local

create_comment

Add a page-level comment to any Docmost page using Markdown. Mention users or pages with special link syntax.

Instructions

Add a page-level comment to a Docmost page, written in Markdown.

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>",
      "markdown": "<markdown>"
    },
    "name": "create_comment"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	The Docmost page ID (UUID) to comment on.
`markdown`	Yes	Comment body as Markdown. Creates a page-level comment (not anchored to a text selection). To tag a user, write a link with a `user:` URL: `[Display Name](user:USER_UUID)` (get USER_UUID from list_workspace_members); `[Title](page:PAGE_UUID)` mentions a page. Tables, images, and task lists are not supported inside comments.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint false) with no destructive or idempotent behavior. The description adds that the comment is page-level (not anchored to text selection), which is valuable behavioral context beyond the annotations. However, it does not disclose success/error details or permission requirements, which are minor given the simplicity.

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 sentence of 12 words, front-loaded with the verb 'Add'. It contains no unnecessary words and every element contributes to the purpose.

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 create tool with 2 well-described parameters and no output schema, the description is largely complete. It explains what the tool does and that comments are page-level. A minor gap is that it does not mention the return value, but this is acceptable given the tool's simplicity and the convention of creation tools returning the created resource.

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%, with both parameters (page_id, markdown) fully described in the schema. The main description does not add additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 'Add', the resource 'page-level comment', the context 'to a Docmost page', and the format 'written in Markdown'. This distinguishes it from siblings like update_comment (modify) and get_comments (read).

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 that this tool is for creating new page-level comments, but it does not explicitly state when to use it versus alternatives (e.g., update_comment for editing, get_comments for reading). No exclusions or prerequisites are mentioned.

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