Skip to main content
Glama

readfetch

readfetch_text

Read-only

Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Fetch a public URL and return its main readable content as Markdown or plain text, plus title, author, published date and site name. Strips navigation, ads and boilerplate. No JavaScript rendering by default (cheaper than readfetch_scrape); one Chromium fallback when plain HTTP is blocked. Prefer readfetch_fetch when you need raw status, headers, or non-HTML bytes; readfetch_scrape when the article only appears after JavaScript runs.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to read.
formatNoOutput flavour: Markdown keeps headings, lists and tables.markdown
max_bytesNoAbort if the response body exceeds this many bytes.
timeout_sNoTotal budget for the whole call in seconds: DNS, redirects, the render fallback and any retry share it.
accept_languageNoAccept-Language header, e.g. 'de-DE,de;q=0.9'. Defaults to en-US.

Output Schema

NameRequiredDescriptionDefault
urlNo
sizeNo
textNo
titleNo
billedNo
formatNo
statusNo
metadataNo
redirectedNo
status_codeNo
requested_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the billing/auth precondition (funded USDC wallet, signing client or proxy, 402 on direct calls), the no-JS-by-default behavior with a single Chromium fallback, and the relative cost versus readfetch_scrape. Those are material facts an agent cannot derive from the structured fields.

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?

Dense and free of filler, but the first two sentences are payment preamble placed ahead of what the tool actually does, delaying the purpose statement. The routing guidance at the end is well placed; only the ordering keeps it from a 5.

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?

Output schema exists, so return values need no explanation, and all five parameters are fully described in the schema. The description fills the remaining gaps an agent needs: auth/payment requirement, cost relative to siblings, retry-capable fallback behavior, and when to choose each alternative 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 description coverage is 100%, so url, format, max_bytes, timeout_s and accept_language are already documented with defaults and bounds. The description only echoes the format choice ('Markdown or plain text') and adds no syntax, units or interaction detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Fetch a public URL and return its main readable content as Markdown or plain text'), plus the returned metadata (title, author, published date, site name) and boilerplate stripping. It explicitly separates itself from readfetch_fetch (raw bytes/headers) and readfetch_scrape (JS-dependent articles), so an agent can pick the right sibling without opening any 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?

Gives explicit routing rules: prefer readfetch_fetch for raw status, headers or non-HTML bytes; use readfetch_scrape when the article only appears after JavaScript runs. It also flags the prerequisite that paid routes need a funded Base USDC wallet and a signing client, and that unsigned direct calls terminate at 402.

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.