Markdown by mdedit.ai

Unpublish a Markdown Document

unpublish_article

Destructive

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.
`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. Dates show when Glama detected each change.

First observedAug 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate destructive=true and readOnly=false, but the description adds critical operational context: the permission scope ('Requires publishing:write') and the mandatory user confirmation step. These are not derivable from annotations and meaningfully shape how an agent should approach the call.

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?

Two sentences with zero fluff. The core purpose is front-loaded, followed by parameter ergonomics and the critical confirmation requirement. Every clause earns its place without redundancy.

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 destructive, permission-gated tool with a required confirmation flag and an output schema available, the description covers the essential invocation requirements. It does not explain the result or side effects in prose, but the output schema likely covers that, so the description is sufficiently complete for an agent to call it correctly.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description's note about preferring natural names over internal IDs is already reflected in the schema descriptions, so it adds no new semantic value beyond a helpful summary of the intended usage pattern.

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 ('Disable a Markdown Document public link') that clearly distinguishes it from siblings like publish_article and edit_article. The purpose is unambiguous and immediately actionable.

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 usage (unpublishing a document) but does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or sibling tools. It gives invocation guidance (accepts natural names) but not selection guidance, so the agent must infer context.

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

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.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools have clearly distinct purposes across article CRUD, review workflows, publishing, and conversion/export. Minor confusion can arise between convert_document and start_article_export (and their corresponding status checkers), but the descriptions explicitly differentiate arbitrary content conversion from exporting stored documents. The render_article tool's broad contextual wording overlaps conceptually with several actions, though its actual function (opening the reader) is unique.

Naming Consistency5/5

All 22 tool names follow a strict snake_case verb_noun pattern, such as list_articles, accept_suggestion, start_article_export, and unpublish_article. There are no mixed conventions, vague verbs, or camelCase outliers, making the naming highly predictable.

Tool Count3/5

At 22 tools, the server sits above the ideal 3-15 range and feels somewhat heavy for an MCP surface. The inclusion of record_article_app_event, a component-only telemetry tool with no agent-facing value, adds to this heaviness. However, the breadth of the domain—documents, collaboration, publishing, and conversion—largely justifies the count.

Completeness3/5

The tool surface covers article lifecycle, review threads, publishing, export/conversion, and presence well, covering most common workflows. A notable gap is the lack of any delete_article or trash operation, leaving no way to remove documents. Additionally, updates are limited to anchored edits via edit_article, with no direct full-content replacement option.

Resources

Need Help?