Markdown by mdedit.ai

Get Markdown Document publish status

get_publish_status

Read-onlyIdempotent

Get the stable public-link URL and publication state for a Markdown Document. Accepts natural workspace names and document titles; internal routing identifiers are optional.

Input Schema

TableJSON Schema

Name	Required	Description
`context`	Yes	Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.
`articleId`	No	Internal document identifier when already available. Omit it when the user referred to the document by title.
`workspaceId`	No	Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces.
`articleTitle`	No	Human-visible document title. Prefer this over asking the user for an internal document identifier.
`workspaceName`	No	Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`fullUrl`	No
`shortUrl`	No
`articleId`	Yes
`publishId`	No
`syncError`	No
`viewCount`	No
`customSlug`	No
`syncStatus`	No
`isPublished`	Yes
`lastUpdated`	No
`publishedAt`	No
`seoMetadata`	No
`workspaceId`	Yes
`sourceVersionId`	No
`sourceContentHash`	No
`lastSuccessfulSyncAt`	No
`sourceArticleRevision`	No
`sourceContentRevision`	No
`sourcePackageRevision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.",
+  "type": "string"
+}

changedInput schema / properties / workspaceId / description

Previous value: -"Internal workspace identifier when already available. Omit it when the user referred to a workspace by name or has only one workspace."New value: +"Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces."

changedInput schema / properties / workspaceName / description

Previous value: -"Human-visible workspace name. Prefer this over asking the user for an internal workspace identifier."New value: +"Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice."

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

First observedAug 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the response surfaces a stable public-link URL plus publication state, which is real but modest added context beyond the annotations and schema.

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?

Two sentences, front-loaded with the core purpose and outcome followed by input-form guidance. No filler or hedging; the only minor redundancy is the second sentence echoing what the schema already states.

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?

This is a simple read-only status lookup: annotations cover safety, all five parameters are fully documented in the schema, and an output schema exists so return values need no prose explanation. The only gap is any explicit routing against the publish/unpublish siblings, which is not strictly required to call the tool 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?

Schema description coverage is 100%, so the schema already documents all five parameters, including the guidance to omit articleId when referring by title and that workspace narrowing is optional. The description's sentence about natural names and optional internal identifiers essentially restates that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get the publish status/publication state of a Markdown Document) and additionally names the payload (stable public-link URL). An agent can distinguish it from the mutating siblings publish_article and unpublish_article, though the description never explicitly contrasts them.

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 tells the agent it can pass natural workspace names and titles with internal routing identifiers optional, which is useful invocation context, but it gives no explicit when-to-use/when-not guidance and never names an alternative (e.g. read_article or the publish/unpublish siblings). Usage is only implied.

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?