Skip to main content
Glama

diogenes-web-scraping-engine-mcp

Web Page Fetcher, Readability Extractor & HTML Parser

scrape_readable_article
Read-onlyIdempotent

Fetches any public HTTP/HTTPS URL and extracts article text, headings, author bylines, and raw html_content. Use as the universal URL fetcher before downstream HTML parsing tools (parse_html_tables, isolate_css_selectors, extract_clean_markdown); for converting full raw HTML without fetching, pass html_content directly. Stateless edge call (max 32 KB, 60 RPM): accepts 'url' or 'html_content' ('readability_profile' defaults to 'article_body_strict'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrape_readable_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe public HTTP or HTTPS web page URL to fetch and extract.
html_contentNoTarget web page HTML containing the article, editorial post, or blog content.
include_bylineNoWhether to parse author names, affiliations, and editorial publication dates.
readability_profileNoContent isolation heuristic: strict article body, technical documentation, or forum thread.

Output Schema

NameRequiredDescriptionDefault
urlNoThe resolved web page URL.
titleYesExtracted main article headline.
bylineYesAuthor credit or publishing editorial team.
excerptYesShort leading synopsis or meta description.
content_textYesSanitized primary article narrative text.
html_contentNoRaw fetched HTML document for piping into downstream HTML parsers.
reading_time_minutesYesEstimated reading duration in minutes based on 220 WPM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "The public HTTP or HTTPS web page URL to fetch and extract.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "html_content"
      -]
    • addedOutput schema / properties / html_content
      Added value: +{
      +  "description": "Raw fetched HTML document for piping into downstream HTML parsers.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / url
      Added value: +{
      +  "description": "The resolved web page URL.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, yet the description still adds real operational context: statelessness, a 32 KB payload cap, 60 RPM throttling, L402 payment at 10 sats, demo mode, and HTTP 400 on invalid input. What it omits is failure behavior beyond the 400 (e.g. paywall, non-HTML content, timeout handling) despite a paywall-bypass sibling existing.

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 purpose, then routing guidance, then operational constraints. Every clause carries information, though the long parenthetical packing limits and payment options into one sentence is denser than ideal and slightly obscures the 32 KB/60 RPM limits.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. Combined with the stated alternatives, defaults, limits, and payment model, an agent has everything needed to call this correctly in a 12-tool scraping suite.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds two things the schema does not express: the either/or relationship between 'url' and 'html_content' (important since zero params are required and the schema leaves the choice ambiguous) and the default value of readability_profile. It also implies include_byline through the 'author bylines' mention.

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 specific verbs and resources: fetches a public HTTP/HTTPS URL and extracts article text, headings, bylines, and raw html_content. It also positions itself against named siblings (parse_html_tables, isolate_css_selectors, extract_clean_markdown), so an agent can distinguish it without reading any schema.

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 designates itself the 'universal URL fetcher' to run before downstream HTML parsing tools, and gives the alternative path — pass html_content directly when you already have raw HTML and want no fetch. Both the when and the when-not are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources