docmost-mcp-remote

Overview Schema Source Related Servers Discussions Admin

Create Upload Link

create_upload_link

Create a time-limited browser link for adding one or more files to a Docmost page without using tokens. Share it so others can drop, order, and insert files directly into the page.

Instructions

Make a link for adding files to a page, and the best way to upload: it costs no tokens. Give the link to the person: they open it in a browser, drop in one or more files, put them in order and press Done, and the files appear in the page. If you can run commands with network access, send files you have yourself with the curl command in the result instead of upload_attachment. The link works for 60 minutes and takes files of up to 50 MB in total; files not added by then are deleted. Anyone with the link can add files to the page until then. Check the outcome with get_upload_status.

Input Schema

Name	Required	Description
`page`	Yes	Page id, slug id or Docmost page URL.
`after_text`	No	Put the files right after the paragraph or block containing this text.
`after_heading`	No	Put the files at the end of the section under this heading (its text).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Oct 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the 60-minute link lifetime, 50 MB total upload limit, deletion of files not added in time, public access for anyone with the link, and the need to verify via get_upload_status. These are important behavioral traits that materially affect safe use.

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?

The purpose and key constraints are front-loaded, and most sentences carry useful information. The workflow sentence is somewhat long and could be tightened, but the description remains appropriately scoped for a tool with security, expiry, and size constraints.

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

Completeness5/5

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

An output schema exists, so return values need not be explained in detail. The description still covers the essential call context: intended recipient workflow, token-free upload path, link expiry, size cap, access model, alternative curl path, and status-check follow-up.

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%, so page, after_text, and after_heading are already documented in the input schema. The description adds workflow context but does not add parameter-specific syntax or placement semantics beyond what the schema provides.

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 states a specific verb and resource: making a link for adding files to a page. It also explicitly contrasts this with upload_attachment and get_upload_status, so an agent can distinguish it from siblings without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explains when to use this tool: to let another person upload files via a browser link, and notes that this avoids token costs. It also names the alternative path (curl with network access instead of upload_attachment) and says to check results with get_upload_status.

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

Deploy Server