Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

web_dev_html_to_markdown

Read-onlyIdempotent

Convert HTML to Markdown using fast regex-based rules, handling headings, bold, italic, links, images, code, blockquotes, lists, and tables. Runs locally and returns Markdown string with stats.

Instructions

HTML to Markdown Converter. Convert an HTML fragment or document into Markdown using fast regex-based rules: headings (h1-h6), bold/italic/strikethrough, links, images, inline code and fenced code blocks, blockquotes, horizontal rules, ordered and unordered lists, and tables (rendered as GFM pipe tables). Unrecognised tags are stripped and HTML entities are decoded. Use this to turn web content, emails, or HTML documents into Markdown; use web_dev_markdown_to_html for the inverse (Markdown to HTML), and webdev_html_minifier when you only want to shrink HTML rather than convert it. Runs locally on the input you provide: read-only, non-destructive, deterministic, offline, contacts no external service, and is rate-limited (anonymous 60 req/min, 500/hr). Returns the Markdown string, a stats object counting converted elements, and the whitespace-normalised source HTML. Note: the three options are accepted for forward compatibility but do not currently change the output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYesThe HTML source to convert. Required and must be non-empty, or a 400 is returned.
optionsNoReserved options. Currently accepted but ignored; output is identical whether or not they are set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownNoThe converted Markdown output.
statsNoCounts derived from the input HTML and resulting Markdown.
cleaned_htmlNoThe input HTML with runs of whitespace collapsed and trimmed.
Behavior5/5

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

Adds significant context beyond annotations: runs locally, read-only, non-destructive, deterministic, offline, no external service, rate-limited, and returns specific output structure. No contradiction with annotations.

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 concise paragraphs front-loaded with the main action. Every sentence adds value; no wasted words.

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

Completeness5/5

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

Fully covers purpose, behavior, output format, rate limits, and sibling differentiation. Given the tool's complexity and the presence of an output schema, the description is complete.

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% with descriptions and examples. The description does not add new semantic info beyond what the schema already provides for the two parameters. Baseline 3 is appropriate.

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 it converts HTML to Markdown using regex-based rules, lists supported elements, and distinguishes from sibling tools by naming web_dev_markdown_to_html for the inverse and webdev_html_minifier for shrinking HTML.

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?

Explicitly tells when to use this tool (convert web content, emails, HTML documents) and when to use alternatives (web_dev_markdown_to_html, webdev_html_minifier). Also clarifies that options are accepted but ignored for forward compatibility.

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/Jambozx/onlinecybertools-mcp-server'

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