Skip to main content
Glama
Sign In
MarkItDown MCP Server

MarkItDown MCP Server

by trsdn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

convert_directory

Convert all files in a directory to Markdown, including PDFs, Office documents, and audio files. Batch processing for efficient format conversion.

Instructions

Convert all supported files in a directory to Markdown

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_directory": "<input_directory>"
    },
    "name": "convert_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_directoryYesPath to the input directory
output_directoryNoPath to the output directory (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.3/5.0
Behavior2/5

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

Minimal behavioral disclosure beyond basic conversion; no details on default output directory, overwrite behavior, error handling (e.g., unsupported files), or performance implications.

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?

Single sentence effectively communicates the core function with no wasted words.

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?

Adequate for a simple tool but missing details like subdirectory handling, supported file list, and return value; output schema absent but not required.

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 100%, so baseline is 3; description adds no extra meaning beyond the schema (e.g., no examples or constraints for 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?

Clearly states it converts all supported files in a directory to Markdown, distinguishing it from sibling convert_file (single file) and list_supported_formats (listing formats).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (convert_file, list_supported_formats), nor any context about prerequisites or when not to use it.

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

Deploy Server

Other Tools