Converts HTML into clean Markdown or plain text, keeping formatting or stripping it entirely, for use in docs, notes, or AI workflows. Accepts up to 50 KB per call.
Convert HTML to clean Markdown or plain text. Same engine as the Clean Copy browser extension. Max 50 KB of HTML per call.
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | The HTML to convert. | |
| mode | No | markdown (default) keeps formatting; plain strips it all. |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral burden. It usefully discloses a hard input ceiling (50 KB per call), which is real operational context, but says nothing about how malformed HTML, scripts/styles, or oversized input are handled, nor what the failure mode looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, zero filler, and the core conversion capability is front-loaded. Each sentence carries distinct information (capability, provenance, limit).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter transform with no output schema, the definition covers what the tool does, its output modes, and its size constraint. It is nearly complete, with the only shortfall being unaddressed error/failure behavior for invalid or oversized input.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the mode enum is already fully explained in the schema ('markdown (default) keeps formatting; plain strips it all'). The description's 'Markdown or plain text' adds nothing beyond that, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description pairs a specific verb (convert) with a specific resource (HTML) and names both output formats (Markdown, plain text). An agent knows exactly what this tool produces before opening the schema, and it is clearly distinct from the security/compliance siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit statement of when to use this tool versus alternatives, nor any when-not guidance or prerequisites. The 'Clean Copy browser extension' reference is provenance trivia, not routing guidance, and the mode choice is left to the parameter schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.