Skip to main content
Glama

Read a web page as markdown

web_read

Read public pages as Markdown with title, language and word count. GET accepts one URL; POST or MCP accepts one URL or an array of up to five in url. An array returns pages in input order. The flat price covers the entire call. A batch fails without settlement if any page cannot be read. No JavaScript rendering, account or API key. $0.0025 per call, paid over x402 (USDC).

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

Input Schema

NameRequiredDescriptionDefault
urlYesA public HTTP/HTTPS URL. POST and MCP also accept an array of up to five URLs.
linksNoAlso return the outbound links as a list. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"The page to read. http and https only; private and loopback addresses are refused."New value: +"A public HTTP/HTTPS URL. POST and MCP also accept an array of up to five URLs."
    • addedInput schema / properties / url / oneOf
      Added value: +[
      +  {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "maxLength": 2048,
      +      "type": "string"
      +    },
      +    "maxItems": 5,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / url / type
      Removed value: -"string"
  2. Added

TDQS

A3.8/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 meaningful behavior: no JS rendering, no account or API key required, a flat $0.0025 per-call price paid over x402 in USDC, and atomic batch semantics ('a batch fails without settlement if any page cannot be read'). What it omits are operational traits an agent would want — redirect handling, robots.txt restrictions, page size/truncation limits, and error shapes for individual failures.

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 core purpose, then constraints, then pricing — every sentence carries information and nothing is padded. The transport sentence ('GET accepts one URL; POST or MCP accepts one URL or an array of up to five in url') is terse to the point of being slightly awkward to parse.

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 compensates by naming the returned fields and the optional outbound-links list. For a two-parameter fetch tool it is nearly complete, with only limits on page size and per-URL error reporting left unstated.

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 beyond the schema: array results are returned in input order, and the scalar-vs-array form is transport-dependent (GET vs POST/MCP). The second parameter, `links`, is documented only in the schema and never mentioned in the description.

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 ('Read public pages as Markdown') and previews the return payload (title, language, word count), so the agent knows exactly what it gets back. It never names or contrasts with the closest sibling, web_status, leaving the read-page vs check-status distinction to inference.

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 concrete selection context: GET takes a single URL, POST/MCP take one URL or an array of up to five, and no JavaScript rendering is performed — an implicit 'do not use for SPA-rendered pages' exclusion. It stops short of explicitly naming when to prefer web_status or another fetch tool 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