Skip to main content
Glama
v1nvn

readability-mcp

by v1nvn

Convert HTML fragment to Markdown

html_to_markdown

Convert arbitrary HTML to Markdown without Readability article scoring. Ideal for snippets already extracted via browser tools.

Instructions

Convert an arbitrary HTML fragment to Markdown WITHOUT Readability article extraction (e.g. a snippet already isolated via chrome-devtools). Same Turndown + DOMPurify path as extract. The server fetches nothing: html is the only source, and url (optional) absolutizes relative links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gfmNoEnable GitHub-Flavored Markdown: tables, strikethrough, and task lists.
urlNoOrigin URL for absolutizing relative links and images. NEVER fetched — origin context only.
htmlYesHTML fragment to convert to Markdown. No Readability article scoring is applied — the fragment is normalized and converted as-is.
formatNoReturned payload format: 'markdown' (default), 'html', 'text', or 'json' (emits {metadata, content, diagnostics}).markdown
imagesNoImage handling: 'keep' (inline ![alt](url)), 'drop', 'src-only' (bare URL text), or 'reference' (link-reference style).keep
maxCharsNoTruncate markdown/text output at a block boundary; never splits a fenced code block. Ignored for html/json formats.
sanitizeNoRun DOMPurify over the extracted/fragment HTML before conversion (strips scripts, event handlers, and iframes).
selectorsNoScope the extracted/converted content by CSS selector before processing.
cleanChromeNoStrip browser chrome (scrollbars, consent/cookie banners, fixed nav and overlays) before conversion. These elements poison Readability density scoring and clutter fragment output.
headingStyleNoMarkdown heading style: 'atx' (#) or 'setext' (underlining with = / -).atx
metadataModeNoPrepend a metadata block to the markdown/text payload: 'none' (default), 'yaml', or 'json'.none
codeBlockStyleNoMarkdown code-block style: 'fenced' (triple backticks) or 'indented' (four-space).fenced
wordsPerMinuteNoReading speed (words per minute) used to compute metadata.readingTimeMin.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe human/LLM-readable payload — Markdown/html/text, or the serialized JSON when format=json.
metadataYesResolved article metadata. Each field is the first non-empty value across a priority cascade.
diagnosticsYesPipeline telemetry describing what was extracted, sanitized, and removed.
schemaVersionYesStructured-content schema version. Bumps only on breaking shape changes to this object.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions using the same Turndown + DOMPurify path as `extract`, implying sanitization, but does not disclose any potential side effects, error behavior, or edge cases. Adequate but minimal.

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, both front-loaded with the core differentiator (no Readability) and usage context. Every word earns its place; no fluff.

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?

Given the tool has 13 parameters, an output schema, and sibling tools, the description is brief but hits the critical distinction. It explains the input constraints and the relationship to `extract`. Some edge cases (e.g., format handling, error scenarios) are left implicit, but output schema covers return structure. Adequate for the complexity.

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. The description adds modest value by clarifying that `url` is only for absolutizing relative links and that the server does not fetch it, which reinforces the 'no fetch' behavior. No other parameter details beyond schema.

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 tool converts HTML fragments to Markdown without Readability extraction, and explicitly distinguishes it from the sibling tool `extract` by specifying the use case (already isolated snippet).

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

Usage Guidelines5/5

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

The description explicitly tells when to use (snippet isolated via chrome-devtools) and when not to (no Readability article extraction), and directly references the sibling tool `extract` as the alternative. The 'server fetches nothing' line further clarifies input constraints.

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/v1nvn/readability-mcp'

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