Skip to main content
Glama

scrape_url

Bypass Cloudflare Turnstile and WAF protections to fetch protected web pages and extract clean, LLM-ready Markdown, text, or raw content for AI agents.

Instructions

Anti-Bot Web Access & Scraper Oracle. Bypasses Cloudflare Turnstile/WAF and extracts clean, LLM-ready Markdown with SHA-256 oracle attestation. Cost: $0.02 USDC or 0.00015 SOL.

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_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget HTTP/HTTPS URL to scrape
payment_txNoSolana signature or Base 0x transaction hash for x402 payment (0.00015 SOL or 0.02 Base USDC)
strip_mediaNo
extract_modeNomarkdown
session_tokenNoPrepaid ScanPay session voucher token (sp_sess_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/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 disclose important behavior: anti-bot bypass, Markdown output, SHA-256 attestation, and a specific price in two currencies. It omits what happens when no payment is supplied, whether payment is required before or after scraping, rate limits, or failure modes – significant gaps for a paid mutation-ish operation.

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?

Two tight sentences, capability first and price second, with no filler beyond the self-aggrandizing 'Oracle' branding. Front-loading is good.

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?

For a five-parameter, no-annotation, no-output-schema tool this is only partially adequate: purpose, output format, and cost are covered, but the payment/session flow and the two content-shaping parameters remain unexplained. An agent can call it with just a URL but cannot confidently choose extract_mode or understand the payment precondition.

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

Parameters2/5

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

Schema coverage is only 60%, so the description should compensate, but it only restates the price that payment_tx encodes. strip_media, extract_mode (the sole enum), and session_token (how to obtain sp_sess vouchers) are left entirely to the schema's terse or absent descriptions.

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?

States a concrete verb and resource ('Web Access & Scraper', 'extracts clean, LLM-ready Markdown') plus a distinguishing capability, anti-bot bypass, that separates it from generic fetch tools. The marketing framing ('Oracle') adds noise but does not obscure what the tool does.

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?

Implies the right usage context via 'Bypasses Cloudflare Turnstile/WAF' – reach for this when a page is bot-protected – and surfaces the paid cost up front. It never says when not to use it, gives no alternative among the listed siblings, and never explains the payment options (payment_tx vs session_token) as a precondition.

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