web2md

web2md_convert

Convert any public URL to clean, readable Markdown. Strips ads, navigation, and boilerplate. Returns LLM-ready text for RAG, research, and content extraction. Free: 10/day. Unlimited: set WEB2MD_LICENSE_KEY env var. Buy: https://grantshatz.gumroad.com/l/mpkqyq ($1+)

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": {
      "url": "<url>"
    },
    "name": "web2md_convert"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 2, 2026

removedInput schema / properties / license_key

Removed value: -{
-  "description": "Optional Gumroad license key for unlimited access",
-  "type": "string"
-}

removedInput schema / properties / url / description
```
Removed value: -"The URL to convert to Markdown"
```
addedInput schema / properties / url / title
```
Added value: +"Url"
```
addedInput schema / title
```
Added value: +"web2md_convertArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "web2md_convertOutput",
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.1/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 free-tier rate limit (10/day), the auth mechanism (WEB2MD_LICENSE_KEY env var), and the content-stripping behavior. It omits failure modes such as paywalled, private, or script-rendered pages, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and transformation, then supporting context. The trailing pricing/purchase sentence is promotional but compact and does carry the free-vs-unlimited distinction, so it earns most of its space.

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?

An output schema exists, so return values need no explanation. Purpose, behavior, rate limits, and licensing are all covered; only edge-case failure behavior and per-URL scope limits are left unstated.

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 description coverage is 0% for the single 'url' parameter, so the schema offers nothing. The description partially compensates by specifying the URL must be public, but adds no format, encoding, or validation guidance beyond that; minimal for a one-parameter tool.

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 ('Convert any public URL to clean, readable Markdown') plus the transformation performed (strips ads, navigation, boilerplate). No siblings exist to disambiguate, and the output format is explicit, so an agent can select it without opening the schema.

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?

Names concrete target scenarios ('RAG, research, and content extraction') and the 'public URL' constraint, which is the key gating condition. It stops short of explicit exclusions (paywalls, JS-heavy, authenticated pages) or alternatives, but there are no sibling tools to route between.

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

All web2md tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.