Skip to main content
Glama

Page extract

page_extract
Read-onlyIdempotent

Render any public web page in a real headless Chrome and return its text. JavaScript runs first, so docs sites and single-page apps that a plain fetch returns empty come back complete. $0.009 per call (x402 on Arc/Base/Solana/X1): the full text and every outbound link. Without a payment the call returns the price and every rail we accept. Refuses private and reserved addresses and our own hosts, so it cannot be used as a proxy into a network. Sites that put a bot wall in front of their pages (Cloudflare, DataDome and the like) answer with a challenge rather than the page: the call then FAILS with http-403 or bot-challenge and says so, rather than charging you for a spinner.

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

Input Schema

NameRequiredDescriptionDefault
urlYesthe http(s) page to render
fullNotrue asks for the paid full text. Without a payment you get a 402 carrying the price and every rail we accept; sign it and call again with `payment`.
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call - you never have to leave MCP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well past the annotations: it discloses per-call pricing ($0.009, x402 on four rails), the 402-with-price behavior when unpaid, SSRF-style refusal of private/reserved/own hosts, and the exact failure codes for bot walls, explicitly saying you are not charged for a challenge. The readOnly/openWorld annotations only say the call is safe and open-world; the description supplies cost, error, and anti-abuse semantics an agent needs before calling.

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 capability, then cost, then security posture, then failure modes — a sensible order with no filler sentences. It is dense and slightly long, with the rail list parenthetical adding bulk, but every sentence carries operational information.

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?

There is no output schema, and the description covers the return ('the full text and every outbound link') as well as the error surface and payment flow, which is nearly all an agent needs to select and invoke it. Minor gaps: no note on rate limits, response size, or redirect handling, and the return shape is described only loosely without an output schema to lean on.

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 real meaning around `full` and `payment`: the actual price, the 402-then-sign retry cycle, and that payment completes inside the tool call without leaving MCP. That deepens the payment parameter beyond what the schema states, though it does not restate the `url` constraints (http/https) itself.

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 specific verb and resource — 'render any public web page in a real headless Chrome and return its text' — plus the JS-rendering differentiator that a plain fetch lacks. It never names its siblings (site_extract, web_read), so the agent must infer why it would pick this one over them. Clear purpose, but sibling differentiation is left implicit.

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?

Gives a concrete when-to-use case (docs sites and SPAs that a plain fetch returns empty) and a hard when-not (bot-walled sites fail with http-403 or bot-challenge rather than returning content). It also lays out the payment path. It stops short of saying when to prefer site_extract or web_read instead.

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