Skip to main content
Glama
guanweiqiang

document-converter-mcp

by guanweiqiang

Batch Convert Documents

batch_convert
Read-only

Convert all files in a directory from one format to another, continuing even if some files fail. Supports recursive subdirectories.

Instructions

Convert all matching files in a directory from one format to another. Individual file failures do NOT abort the entire batch. Arguments:

  • inputDir (string, required): Source directory (relative to workspace)

  • outputDir (string, required): Destination directory (relative to workspace)

  • from (enum, required): Source format — 'md', 'markdown', 'docx', or 'pdf'

  • to (enum, required): Target format — 'md', 'markdown', 'docx', 'pdf', or 'html'

  • recursive (boolean, optional): Traverse subdirectories. Defaults to false

  • overwrite (boolean, optional): Overwrite existing files. Defaults to false

  • cleanForLLM (boolean, optional): Clean Markdown output for LLM consumption

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputDirYesSource directory path (relative to workspace)
outputDirYesDestination directory path (relative to workspace)
fromYesSource file format
toYesTarget file format
recursiveNoTraverse subdirectories recursively
overwriteNoOverwrite existing output files. Defaults to false.
cleanForLLMNoClean Markdown output for LLM consumption
Behavior1/5

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

Description contradicts annotations: 'Convert' implies mutation but readOnlyHint=true declares read-only. Also no mention of error handling beyond individual failures not aborting batch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is structured but verbose; parameter list duplicates schema content. Could be more concise while preserving key behavioral notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all seven parameters and highlights batch failure behavior, but lacks description of return values or error handling beyond individual failures, leaving some context incomplete.

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%, but description adds meaning: clarifies paths are relative to workspace, lists allowable enum values, and specifies defaults for optional boolean parameters.

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 'Convert' and the resource 'all matching files in a directory', distinguishing it from sibling single-format conversion tools.

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 use for batch conversions but does not explicitly specify when to use this tool versus sibling single-file tools or mention any exclusions or prerequisites.

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/guanweiqiang/document-convert-mcp'

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