Skip to main content
Glama

web2md

by io.github.astra-intelligence
OverviewDiscussionsAdmin

Server Details

Convert any URL to clean Markdown. Free tier: 10/day. Unlimited via Gumroad license.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
66.1% over 18 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
astra-intelligence/web2md-mcp
GitHub Stars
0

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are unambiguously distinct: one converts a single URL, the other converts a batch. There is no overlap that could cause misselection, and the descriptions make the single-vs-batch boundary explicit.

Naming Consistency5/5

Both names follow the identical web2md_ prefix plus a clear convert/convert_batch pattern. The convention is predictable and consistent across the entire surface.

Tool Count4/5

Two tools is on the thin side, but for a focused URL-to-Markdown service the single/batch split is a natural and sufficient division. No filler tools are present.

Completeness4/5

Single and batch conversion cover the core use case, with per-URL success flags in the batch response. Minor gaps exist (e.g. no options for output formatting or metadata), but agents can work around these.

Available Tools

2 tools
web2md_convertAInspect

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+)

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

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.

web2md_convert_batchAInspect

Convert multiple public URLs to clean Markdown in one call (Web2MD Pro). Requires a WEB2MD_LICENSE_KEY env var (buy: https://grantshatz.gumroad.com/l/mpkqyq $1). Returns a list of {url, success, markdown} results. Free tier is single-URL only.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and discloses the license-key requirement, purchase URL, output shape, and free-tier limitation. It does not cover rate limits, maximum batch size, or per-URL failure behavior beyond the success flag, but the core behavior is well exposed.

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?

The description is appropriately short and front-loads the core action and batching scope. The purchase link is useful for auth but slightly promotional, keeping it from a perfect score.

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 output schema exists, the description need not explain return values but does so anyway, and it adds necessary license context with no annotations available. Missing details about maximum batch size and per-URL error handling prevent a perfect score.

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 urls parameter, so the description must add meaning. It clarifies that urls is a collection of public URLs and that the result is a list, but it does not specify format constraints, batch size, or examples beyond the schema's array type.

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 states a specific verb (convert), resource (multiple public URLs), output format (clean Markdown), and batching scope ('in one call'). It distinguishes itself from the single-URL sibling by noting 'Free tier is single-URL only,' making the batch distinction unambiguous.

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 gives clear context: this tool requires a WEB2MD_LICENSE_KEY env var and is for multiple URLs, while the free tier is single-URL only. It does not explicitly name the sibling tool as the alternative, but the condition for choosing batch vs. single is effectively communicated.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedweb2md_convert_batch
  2. 1 tool update
    • Changedweb2md_convert5 fields changed
      • 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"
+}
  3. 1 tool update
    • First observedweb2md_convert

Related MCP Connectors

Related MCP Servers

Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources