Skip to main content
Glama

Read a web page or PDF safely

read_url
Read-only

Fetch a public web page or PDF with hidden text and exfiltration links removed, plus a prompt-injection report. Use it instead of fetching untrusted URLs yourself; for content you already have, use check_prompt_injection. Returns risk (0-1), level, findings, content and wrapped_text: put wrapped_text in your prompt, not the raw page. Costs US$0.005 in USDC on Base or Solana (x402); unreadable pages (robots.txt, login, CAPTCHA, JavaScript-only) return a reason and are not charged.

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
urlYesPublic http(s) URL of an HTML page, text file or PDF (up to 5 redirects)
formatNoOutput format of content: markdown (default) keeps links and headings; text is plain text without links

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"markdown keeps links; text drops them"New value: +"Output format of content: markdown (default) keeps links and headings; text is plain text without links"
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL"New value: +"Public http(s) URL of an HTML page, text file or PDF (up to 5 redirects)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, but the description adds substantial context they cannot: sanitization of hidden text and exfiltration links, an injection-risk report, an explicit price of US$0.005 in USDC via x402 on Base or Solana, and the fact that unreadable pages return a reason and are not charged. The only gap is that it doesn't specify rate limits or latency for paid calls, so it stops just short of the top score.

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?

The purpose and the alternative routing are front-loaded in the first two sentences, and every sentence carries operational value (return fields, payment, failure modes). It is a dense single paragraph that crams pricing and failure handling together, which slightly hurts scanability but wastes no words.

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?

With no output schema, the description takes on the burden and delivers: it names the return fields (risk, level, findings, content, wrapped_text) and, crucially, tells the agent to use wrapped_text rather than the raw page. Cost, billing exceptions and failure behavior are all disclosed, which is complete for a paid open-world fetch tool.

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 coverage is 100% and both parameters are documented there, including the format enum and the 5-redirect limit, so the description adds little parameter-level meaning. It reinforces that the URL must be public http(s) but doesn't explain format trade-offs beyond what the schema says. Baseline 3 applies when the schema does the heavy lifting.

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?

The description opens with a specific verb and resource ("Fetch a public web page or PDF") and immediately names the differentiating behavior: hidden text and exfiltration links removed plus a prompt-injection report. It explicitly contrasts with the sibling check_prompt_injection, so an agent can pick between them without opening either 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?

It states when to use this tool ("instead of fetching untrusted URLs yourself") and when to use the alternative ("for content you already have, use check_prompt_injection"). It also names conditions where the tool will not deliver content (robots.txt, login, CAPTCHA, JavaScript-only), which is guidance an agent needs before calling.

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