Skip to main content
Glama

Web Read - URL to clean Markdown or text for LLMs

web_read
Read-onlyIdempotent

Fetch any public web page and return its main content as clean Markdown (or plain text) with title, author, date and language. Boilerplate (menus, cookie banners, footers) removed. Respects robots.txt. ~1-3 s. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/web-read.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://en.wikipedia.org/wiki/HTTP_402",
      "format": "markdown"
    },
    "name": "web_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL (https://...)
formatNomarkdown or textmarkdown
maxCharsNoCut the content after this many characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the bar is lower, yet the description still adds real context: boilerplate stripping, robots.txt compliance, ~1-3 s latency, and the 25 calls/day free cap plus x402 per-call pricing. It stops short of saying what happens when robots.txt disallows a fetch or when the request fails, so it misses full behavioral coverage.

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?

Four compact sentences, front-loaded with the core action and output, followed by processing behavior, constraints, and cost. Every sentence carries distinct information; nothing is redundant with the title or schema.

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?

With no output schema, the description correctly takes on the return-value burden by listing the fields returned (content, title, author, date, language). Minor gaps remain around truncation semantics for maxChars and error/blocked-response behavior, but for a simple 3-parameter fetch tool this is nearly complete.

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%, so all three parameters (url, format, maxChars) are already documented, establishing a baseline of 3. The description adds only a restatement of the format choice ('Markdown (or plain text)') and says nothing about maxChars truncation behavior, so it does not meaningfully exceed the schema.

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+resource ('Fetch any public web page') and specifies the transformation and return payload ('main content as clean Markdown (or plain text) with title, author, date and language'). An agent can tell this extracts page content rather than producing an analysis report, but the description never explicitly contrasts itself with siblings like web_page_report or website_report, leaving that differentiation implicit.

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?

'Fetch any public web page' and 'Respects robots.txt' imply the appropriate context (public pages only, no auth-walled content), and the pricing line hints at free-tier limits. However, there is no explicit when-to-use/when-not guidance and no named alternative for cases such as pages behind auth, JS-only rendering, or when the caller wants an evaluated report instead of raw content.

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