Skip to main content
Glama
Sign In
HatFetch

HatFetch

Official
by ProxyHatCom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape a web page to Markdown

scrape

Fetch a URL and return its content as clean, LLM-ready Markdown. Automatically renders JavaScript and bypasses bot detection for any single page.

Instructions

Fetch a single URL and return its content as clean, LLM-ready Markdown. Renders JavaScript sites and gets past bot detection automatically: tries a fast HTTP fetch, then escalates to a real stealth browser through residential proxies when a page is an empty JS app or is blocked (Cloudflare, DataDome, 403/429). Use for docs, articles, product pages, SPAs, or any single page.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL to fetch.
renderNoHow to fetch. 'auto' (default): HTTP first, escalate to a real browser if needed. 'http': fast, HTTP only. 'browser': force full JS rendering + stealth fingerprint.
onlyMainContentNoExtract just the main article/content, stripping nav/ads/footer. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Discloses automatic escalation from HTTP to browser with stealth proxies for JS rendering and bot detection bypass. No annotations present, so description carries full burden; missing potential failure or rate limit info.

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 sentences front-loaded with main purpose, no fluff. Every sentence adds necessary context.

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?

Covers purpose, usage, behavior, and parameter details adequately for a simple fetch tool without output schema. Could mention error handling or timeouts.

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%, baseline 3. Description adds value by explaining 'render' enum behaviors (auto, http, browser) and 'onlyMainContent' default, going beyond schema.

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?

Clearly states the tool fetches a single URL and returns LLM-ready Markdown. Distinguishes from siblings 'crawl' and 'screenshot' by specifying single-page focus and output format.

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?

Explicitly says 'Use for docs, articles, product pages, SPAs, or any single page,' providing clear context. Lacks explicit exclusions but effectively implies appropriate use cases.

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