Markdown by mdedit.ai

Convert a document to another format

convert_document

Read-only

Convert Markdown or HTML you already have into Word, PDF, HTML, LaTeX, EPUB and other formats. Pass the content directly; the document does not need to exist in mdedit. Conversion is asynchronous: pass the returned opaque jobId to get_conversion_status until it completes, and never show that identifier to the user. To export a document already stored in mdedit, use start_article_export instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	Target format, for example docx, pdf, html, latex, epub.
`from`	No	Format of the supplied content.	markdown
`content`	Yes	The Markdown or HTML to convert.
`context`	Yes	Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.
`fileName`	No	Name for the converted file.

Output Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	Opaque conversion handle required by get_conversion_status. Use it for polling, but never show it to the user.
`format`	Yes
`status`	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: -[
-  "content",
-  "to"
-]New value: +[
+  "content",
+  "to",
+  "context"
+]

AddedAug 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the operation is asynchronous, a jobId is returned and must be polled, and it must never be shown to the user. It does not cover error or format-rejection behavior, so it falls short of exhaustive.

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: capability, invocation/privacy handling, and sibling routing. The important scope constraint is front-loaded.

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 an async conversion tool with an output schema and full annotation coverage, the description supplies the workflow and routing context an agent needs. It stops short of describing supported-format limits or failure modes, but return values are already covered by the output schema.

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 all five parameters are documented structurally. The description adds only a little beyond that ('Pass the content directly; the document does not need to exist in mdedit') and says nothing about the 'context' or 'from' semantics. Baseline 3 is appropriate.

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?

States a specific verb ('Convert') and resource (Markdown/HTML content into Word, PDF, HTML, LaTeX, EPUB), and distinguishes itself from the sibling start_article_export. An agent can tell exactly what this does without opening the schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly ('To export a document already stored in mdedit, use start_article_export instead') and gives the routing condition. It also explains the follow-on step via get_conversion_status, so the full workflow is clear.

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?