Skip to main content
Glama

Markdown to Word Converter

create_word_from_markdown

Convert markdown content to a formatted Word document. Supports headings, lists, tables, images, block quotes, page breaks, and inline formatting.

Instructions

Converts markdown content to a professionally formatted Word (.docx) document. Supports headings, lists, tables, images, block quotes, page breaks, horizontal lines, text alignment, and rich inline formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoDocument title (shown in file properties)
authorNoDocument author name (shown in file properties)
subjectNoDocument subject/description (shown in file properties)
file_nameNoCustom filename for the output file (without extension). If not provided, a unique identifier will be used.
footer_textNoText for document footer (bottom of every page). Use {page} for auto page number, {pages} for total pages.
header_textNoText for document header (top of every page). Use {page} for auto page number, {pages} for total pages.
include_tocNoIf true, inserts a Table of Contents at the beginning of the document. The TOC updates automatically when opened in Word.
markdown_contentYesMarkdown content for the document body. Separate all block elements with blank lines. BLOCK ELEMENTS (each on its own line): - Headings: # H1, ## H2, ### H3, #### H4, ##### H5, ###### H6 - Unordered lists: - item (or * or +); nest with 3-space indent - Ordered lists: 1. item, 2. item; nest with 3-space indent - Tables: | H1 | H2 |\n|---|---|\n| C1 | C2 | (cells support inline formatting) - Block quotes: > text (supports inline formatting) - Page break: --- (three+ dashes alone on a line — starts new page) - Horizontal line: *** (three+ asterisks alone on a line — visual separator) - Images: ![alt text](url) INLINE FORMATTING (usable in paragraphs, headings, lists, tables, quotes): - **bold**, *italic*, ***bold italic*** - ~~strikethrough~~, __underline__ (double underscore — NOT bold) - `code` (Courier New font) - [link text](https://url) - Nesting: **bold with *italic* inside**, *italic with **bold** inside* - Combinations: **~~bold strikethrough~~**, **__bold underline__**, *~~italic strikethrough~~* - Escaped literals: \* \** \` to render *, **, ` without formatting TEXT ALIGNMENT (HTML tags): - <center>text</center> or multi-line: <center>\nline1\nline2\n</center> - <div align="right|center|justify|left">text</div> (single or multi-line) LINE BREAKS: End a line with two trailing spaces for a soft break within the same paragraph. CONVENTIONS: - Do NOT confuse --- (page break) with *** (horizontal line). - Do NOT confuse __underline__ with bold; always use **bold** for bold. - LEGAL CONTRACTS: use numbered lists (1., 2., 3.) for clauses, nested lists for provisions; use headings only for the contract title. - Other documents: use headings (# ## ###) to organize sections.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations are minimal (title only). The description lacks disclosure of side effects (e.g., file creation location, permissions needed) and processing context. It focuses on formatting features.

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, front-loaded with key information, no wasted words. The core purpose and supported features are stated efficiently.

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?

Covers core functionality and supported features well. Could be improved by mentioning output behavior (e.g., where the .docx is saved) and error handling. Output schema likely supplements completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description provides extensive formatting rules for markdown_content, adding significant value beyond the schema parameter descriptions.

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 clearly states the verb 'Converts' and resource 'markdown content to a professionally formatted Word (.docx) document'. It lists supported features, distinguishing it from siblings like create_pdf_from_markdown.

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?

No explicit guidance on when to use or when not to use this tool versus alternatives. The purpose implies use for Word conversion, but no exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/filhocf/docforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server