dochost-mcp

Publish to dochost

publish

Publish Markdown or HTML as a hosted dochost page and get a shareable URL. Respects your plan: link lifetime, password protection, custom slug, and branding all follow your account entitlements. Paid plans publish without dochost branding by default — pass noBranding: false to keep the mark. The link is issued on the account's primary host (a custom domain or subdomain when one is set in Settings › Domains, otherwise dochost.co/d); get_account reports which.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`body`	Yes
`format`	No
`public`	No
`password`	No
`customSlug`	No
`noBranding`	No

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The shareable page URL, on the account's primary host (custom domain, subdomain, or dochost.co/d). Relay it verbatim.
`note`	No	Free-tier only: expiry warning + upgrade link. Relay this to the user.
`slug`	Yes
`format`	Yes
`expiresAt`	No	ISO timestamp, or null when the link is permanent.
`permanent`	Yes
`iterateHint`	No	How to revise this page later. Follow it instead of publishing a second time.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026

changedOutput schema / properties / url / description

Previous value: -"The shareable dochost.co page URL."New value: +"The shareable page URL, on the account's primary host (custom domain, subdomain, or dochost.co/d). Relay it verbatim."

Changed1 schema field changedJul 27, 2026

addedOutput schema / properties / iterateHint

Added value: +{
+  "description": "How to revise this page later. Follow it instead of publishing a second time.",
+  "type": "string"
+}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Free-tier only: expiry warning + upgrade link. Relay this to the user.",
+  "type": "string"
+}

Changed1 schema field changedJun 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "expiresAt": {
+      "description": "ISO timestamp, or null when the link is permanent.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "format": {
+      "enum": [
+        "markdown",
+        "html"
+      ],
+      "type": "string"
+    },
+    "permanent": {
+      "type": "boolean"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "url": {
+      "description": "The shareable dochost.co page URL.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "slug",
+    "format",
+    "permanent"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate this is not read-only and not destructive, and the description adds useful behavioral context: plan-dependent lifetime, password protection, custom slug, branding behavior, and host selection. It does not disclose idempotency or what happens if a customSlug is already taken, but the core behavior is transparent.

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 concise and front-loaded with the core purpose in the first sentence. The remaining sentences add valuable behavioral details without filler, and the structure makes the most important information immediately accessible.

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?

The description covers plan constraints, branding, and host resolution, which are important context for invoking the tool correctly. The output schema covers return values, so the missing parameter-level details are the main gap, but the overall context is sufficient for most usage scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only explains noBranding semantics. The other parameters (body, format, public, password, customSlug) are not described beyond their property names, leaving the agent to infer their exact meaning and constraints.

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 uses a specific verb ('Publish') and resource ('Markdown or HTML as a hosted dochost page') and clearly states the outcome ('get a shareable URL'). It is easy to distinguish from sibling tools like delete_page, get_page, and update_page.

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 intended use is clear: publish new content to a hosted page. However, there is no explicit statement about when to use this tool instead of update_page or how to handle existing pages, and the mention of get_account is informational rather than a usage rule.

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

All dochost-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.