Skip to main content
Glama
ClearFetch - Unblocked Web & Anti-Bot MCP Server

ClearFetch - Unblocked Web & Anti-Bot MCP Server

read_url

Fetch any URL as clean Markdown, bypassing Cloudflare Turnstile, DataDome, and 403 blocks so you can read protected pages without scraping failures.

Instructions

Read any URL as clean, token-optimized Markdown. Reliably bypasses Cloudflare Turnstile, DataDome, PerimeterX, and anti-bot systems where other scrapers fail with 403 Forbidden.

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": "read_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full target URL to read (e.g. https://www.bloomberg.com/news/...)
max_ageNoCache TTL in seconds. 0 forces live fresh fetch.
stealthNo'auto' attempts fast TLS spoofing first and auto-escalates on challenge detection; 'force' routes through full residential browser solver immediately.auto
include_linksNoWhether to return extracted outgoing links.
only_main_contentNoWhether to strip navigation, ads, and footers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one substantive trait: bypassing Cloudflare Turnstile, DataDome, and PerimeterX. However, it omits failure modes, cost/rate limits, handling of authenticated or paywalled pages, non-HTML content, and JS-rendering requirements — all material for a scraping tool.

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 dense sentences, front-loaded with the capability and output format, followed by the differentiator. Nothing is redundant or padded.

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

Completeness3/5

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

The description substitutes partly for a missing output schema by specifying Markdown output, but for a 5-parameter tool with no annotations it leaves notable gaps: no guidance on authenticated URLs, rate limits, or what happens on total failure. Adequate but not complete for the tool's 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 description coverage is 100% and each parameter (max_age, stealth, include_links, only_main_content) is well documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Read') and resource ('any URL') and states the output format ('clean, token-optimized Markdown'), which distinguishes it from extract_structured_data by return type. It does not explicitly contrast with search_and_read, leaving sibling differentiation to inference.

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

Usage Guidelines3/5

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

Usage is only implied: 'where other scrapers fail with 403 Forbidden' suggests using this as a fallback when blocked, but there is no explicit when-to-use/when-not-to-use statement or routing to search_and_read or extract_structured_data. An agent must infer the selection logic.

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

Deploy Server

Other Tools