Markdown by mdedit.ai

Unpublish a Markdown Document

unpublish_article

DestructiveIdempotent

Disable a Markdown Document public link. Accepts natural workspace names and document titles; internal routing identifiers are optional. Requires publishing:write and explicit user confirmation.

Input Schema

TableJSON Schema

Name	Required	Description
`articleId`	No	Internal document identifier when already available. Omit it when the user referred to the document by title.
`commandId`	Yes	Globally unique UUID for this logical publishing mutation. Generate it once and reuse the exact value if the tool call is retried.
`workspaceId`	No	Internal workspace identifier when already available. Omit it when the user referred to a workspace by name or has only one workspace.
`articleTitle`	No	Human-visible document title. Prefer this over asking the user for an internal document identifier.
`workspaceName`	No	Human-visible workspace name. Prefer this over asking the user for an internal workspace identifier.
`confirmUnpublish`	Yes	Must be true after the user confirms that the public link should stop working.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	Yes
`articleId`	Yes
`publishId`	Yes
`workspaceId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

addedInput schema / properties / commandId

Added value: +{
+  "description": "Globally unique UUID for this logical publishing mutation. Generate it once and reuse the exact value if the tool call is retried.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "confirmUnpublish"
-]New value: +[
+  "commandId",
+  "confirmUnpublish"
+]

First observedAug 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructive and non-read-only behavior, and the description adds meaningful context beyond those hints: it requires publishing:write permission and explicit user confirmation. This surfaces the key safety and authorization considerations for a destructive operation.

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, each earning its place: the core effect, the identifier strategy, and the required permission/confirmation. The most important behavioral fact is front-loaded.

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?

For a destructive tool with detailed schema, output schema, and annotations, the description covers the essential operational constraints: what action is performed, how to identify the target, what permission is needed, and that user confirmation is mandatory. Nothing critical is missing.

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 the baseline is 3. The description condenses the identifier-optionality guidance already present in the parameter descriptions but does not add substantial new meaning beyond the schema.

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 opens with a specific action and resource: 'Disable a Markdown Document public link.' This clearly distinguishes the tool from siblings like publish_article and edit_article by describing the unpublishing effect rather than merely restating the name.

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

Usage Guidelines4/5

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

The description gives clear usage context by explaining that natural workspace names and document titles are acceptable and that internal identifiers are optional. It also states the required permission and explicit user confirmation, which are important preconditions, though it does not explicitly name alternatives or exclusion cases.

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

All Markdown by mdedit.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?