docmost-community-mcp

Overview Schema Source Related Servers Discussions Admin

export_page

Read-only

Export a Docmost page to a local Markdown or HTML file, or a ZIP archive when including child pages. Returns the file path and content type for further processing.

Instructions

Export a page to a local file. A page without children is often a .md or .html file; include_children usually returns a zip. Writes to output_path or a temp file and returns the path plus content type.

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": "export_page"
  }
}

Input Schema

Name	Required	Description
`format`	No
`page_id`	Yes	Page UUID or slugId
`output_path`	No	Where to write the exported file
`include_children`	No
`include_attachments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds useful behavior beyond that: it writes to output_path or a temp file, returns path and content type, and explains the zip vs. single-file behavior for include_children. No contradiction.

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?

Three sentences with no fluff; the core purpose is front-loaded and every sentence adds information an agent needs (destination, format behavior, return value).

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 five-parameter tool with no output schema, the description provides the key missing context: where the file goes, what is returned, and how include_children changes the result. It remains slightly incomplete on include_attachments and default boolean behavior.

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 only 40%, so the description needs to compensate. It adds meaningful meaning for include_children (zip behavior) and output_path (temp fallback), but does not clarify include_attachments or how format interacts with include_children.

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?

States a specific action ('Export a page') and destination ('to a local file'), and clarifies output shape (.md/.html vs zip). This clearly distinguishes it from sibling tools such as export_space.

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 explicit guidance on when to choose export_page over alternatives like export_space or get_page. The conditional information about include_children is behavioral rather than tool-selection guidance.

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