dead-letter

Overview Schema Source Related Servers Discussions Admin

Convert email folder

convert_directory

Batch converts .eml emails in a directory to Markdown, mirroring subfolders in a required output directory and returning a JSON summary.

Instructions

Batch convert all .eml files in a directory to Markdown.

Recursively finds .eml files (at most 50 per call; larger directories are rejected before any conversion). output_directory is required: Markdown is written there, mirroring subfolders, and source .eml files are left in place. Returns a JSON summary with total, successes, failures, output_paths, and errors.

Use convert_eml to retrieve individual converted file content.

Input Schema

TableJSON Schema

Name	Required	Default
`preset`	No	default
`dry_run`	No
`directory`	Yes
`thread_mode`	No	latest
`thread_order`	No	oldest-first
`include_raw_html`	No
`output_directory`	Yes
`strip_signatures`	No
`strip_disclaimers`	No
`embed_inline_images`	No
`include_all_headers`	No
`no_calendar_summary`	No
`strip_quoted_headers`	No
`strip_tracking_pixels`	No
`strip_signature_images`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.5Sep 30, 2026
- removedInput schema / properties / output_directory / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / output_directory / default
```
Removed value: -null
```
- addedInput schema / properties / output_directory / type
```
Added value: +"string"
```
- changedInput schema / required
```
Previous value: -[
-  "directory"
-]New value: +[
+  "directory",
+  "output_directory"
+]
```
First observedv0.2.4Jul 10, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 50-file limit, that oversized directories are rejected before any conversion, that source .eml files are left in place (non-destructive), and output folder mirroring. It omits auth requirements, runtime/performance expectations, and what happens on partial failure beyond the 'failures' count.

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 short sentences, each earning its place: the operation and scope, the batch constraint plus output semantics, then the routing hint to convert_eml. Front-loaded with no filler.

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?

The output schema exists, so listing the JSON summary fields is somewhat redundant but harmless, and the write/limit behavior is covered. The real gap is that a 15-parameter tool documents only one parameter, leaving the bulk of configurable conversion behavior unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across 15 parameters, so the description must compensate, yet it only explains output_directory semantics. The 13 remaining options (preset, dry_run, thread_mode/order, and eight strip/include toggles) get no explanation of defaults or effect, leaving the agent to guess at conversion behavior.

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 and resource ('Batch convert all .eml files in a directory to Markdown') and immediately distinguishes itself from the sibling convert_eml by routing single-file retrieval there. An agent can tell exactly what this does versus convert_mbox or convert_eml_to_bundle from the first sentence.

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

Usage Guidelines4/5

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

It names the alternative ('Use convert_eml to retrieve individual converted file content') and gives a clear batch context, plus the 50-file ceiling that defines when this tool is appropriate. It does not, however, explain when to choose this over convert_mbox or convert_eml_to_bundle, so it stops short of full when/when-not coverage.

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

Deploy Server