Markdown by mdedit.ai

Check a Markdown Document export

get_article_export_status

Read-onlyIdempotent

Check an export started by start_article_export. Returns a download resource link when complete without exposing the internal job identifier.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jobId`	Yes
`context`	Yes	Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`fileName`	No
`mimeType`	No
`progress`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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 / required

Previous value: -[
-  "jobId"
-]New value: +[
+  "jobId",
+  "context"
+]

First observedAug 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding behavior beyond them: it returns a download resource link on completion and deliberately withholds the internal job identifier. This gives the agent real expectations about the response's shape and security posture.

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 tight sentences, front-loaded with the action and its prerequisite, then the return behavior. No filler; every clause carries information.

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 two-parameter status-check tool with annotations covering safety and an output schema covering return values, the description supplies the prerequisite, the completion signal, and the withholding behavior. Only labels remain undocumented.

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 50% – the 'context' parameter is documented, but 'jobId' has no schema description. The description partially compensates by linking jobId to an export created by start_article_export, but never clarifies its format or source, and the phrase about not exposing the internal job identifier could confuse which identifier is which.

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 ('Check') and resource ('an export started by start_article_export'), tying it directly to the sibling that initiates the workflow. An agent can distinguish it from start_article_export, though it doesn't contrast with other status-style siblings like get_conversion_status or get_publish_status.

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?

Usage context is implied by 'started by start_article_export', which establishes the prerequisite, but there is no guidance on polling cadence, terminal states, or when to prefer this over the other status tools in the sibling set. Adequate but with clear gaps.

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?