Skip to main content
Glama

readfetch

readfetch_batch

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. Read a fixed list of public HTML pages in one call—the same article extraction as POST /v1/text for each URL (Markdown or plain text plus title and metadata). One x402 payment covers the batch (minimum 3 pages quoted; URLs deduped, max 50). Returns results in input order: each item has url, status_code, text, billed, and hint when undelivered, plus batch-level delivered, failed, billed_pages, and optional credit for unused pages. Undelivered pages are not billed. Use readfetch_text for one URL, readfetch_map then readfetch_crawl to discover and walk a site, readfetch_scrape when JavaScript is required. Read-only; 402 without PAYMENT-SIGNATURE like other paid tools.

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": {
      "urls": "<urls>"
    },
    "name": "readfetch_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs to read, deduped before quoting.
formatNoPer-item output flavour, same as /v1/text: markdown (default) or plain text.markdown
pipelineNotext (default) = HTTP-first per URL, same as readfetch_text; use render when probe reported challenge:true or items need JavaScript — bills like scrape per undelivered page, not like plain text.text
timeout_sNoTotal budget for the whole batch in seconds; every item shares it and no item restarts it.
accept_languageNoAccept-Language header for every item, e.g. 'de-DE,de;q=0.9'. Defaults to en-US when omitted.

Output Schema

NameRequiredDescriptionDefault
creditNo
failedNo
statusNo
resultsNo
deliveredNo
billed_pagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, and the description adds substantial behaviour beyond them: x402 payment gating, one payment covering the batch, minimum 3 pages quoted, max 50 and dedupe, and the key billing rule that undelivered pages are not billed plus a credit for unused pages. It does not contradict the read-only annotation. The only real gap is that it restates return fields that the output schema already covers.

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 payment prerequisite before the tool's actual function, and the sibling-routing sentence is compact and high-value. Some space is spent enumerating return fields (url, status_code, text, billed, hint, delivered, failed, billed_pages, credit) that the output schema already documents, which is wasted for an agent reading structured data.

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?

Covers everything needed to call this correctly: auth/payment path, batch sizing and dedupe, per-item vs batch billing behaviour, partial-failure semantics, and explicit alternatives for the single-URL, discovery, and JS cases. With annotations and an output schema also present, nothing material is missing.

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 baseline is 3; the description still adds meaning beyond the schema by documenting the minimum-3-page quote floor and per-page billed semantics that govern parameter choice (notably that 'pipeline: render' bills like scrape rather than plain text). The max-50 and dedupe details duplicate the schema's urls description and add no new value.

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 ('Read a fixed list of public HTML pages in one call') and pins the semantics to a known operation ('the same article extraction as POST /v1/text for each URL'), including the output flavour (Markdown/plain text plus title and metadata). An agent can distinguish this batch read from readfetch_text/scrape 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: readfetch_text for one URL, readfetch_map then readfetch_crawl to discover and walk a site, readfetch_scrape when JavaScript is required. It also states the prerequisite gate (funded Base USDC wallet / signing client, 402 otherwise) so an agent knows when this call cannot succeed at all.

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.