Skip to main content
Glama

readfetch

readfetch_section

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. Extract one heading or one CSS selector from a public page instead of the whole document. Returns matched Markdown or text, title, chars, content_sha256, and billed. If the heading is missing, returns HTTP 200 with empty text and available_headings so you can retry. mode: fast (plain HTTP) or render (default, Chromium when the page blocks HTTP). max_chars truncates output (default 8000, max 20000). Prefer readfetch_text for full articles; readfetch_scrape when content needs JavaScript.

Input Schema

NameRequiredDescriptionDefault
urlYesPublic page URL to extract from.
modeNofast = HTTP-first; render = one browser pass when plain HTTP fails (default).render
formatNoOutput flavour for the matched section (markdown default).markdown
headingNoHeading text to match (case-insensitive, whitespace-normalised). Required unless `selector` is set — send exactly one of `heading` or `selector`, not both.
selectorNoCSS selector; up to 20 matches concatenated. Required unless `heading` is set — use selector when the section has no stable heading text.
max_charsNoTruncate matched text after this many characters.

Output Schema

NameRequiredDescriptionDefault
urlNo
hintNo
textNo
charsNo
titleNo
billedNo
statusNo
matchedNo
status_codeNo
used_browserNo
content_sha256No
available_headingsNo

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?

The description goes well past the readOnlyHint/openWorldHint annotations: it discloses the paid-route prerequisite (funded Base USDC wallet plus a signing client or proxy), that unsigned calls stop at 402, and the notable edge-case behavior that a missing heading still returns HTTP 200 with empty text plus available_headings. The one thing left implicit is anything about rate limits or billing magnitude beyond the 'billed' field name.

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?

Almost every sentence carries load — the payment precondition, the one-of parameter rule, the empty-result recovery, and the sibling routing are all things an agent needs. The only structural weakness is that it opens with an auth wall rather than the tool's purpose, so the core verb arrives second.

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?

For a read-only extraction tool with a full output schema, six well-documented parameters, and two enums, the description covers purpose, routing, preconditions, failure modes, and truncation. Nothing an agent needs in order to call it correctly or interpret an empty result 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 already 100%, so the baseline is 3, but the description adds decision-level meaning: mode is framed as when Chromium is engaged ('when the page blocks HTTP') and max_chars as a truncation ceiling with a usable default. Those are marginal restatements of schema text rather than new syntax, keeping it below a 5.

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 names a specific verb and resource ('Extract one heading or one CSS selector from a public page instead of the whole document') and scopes it tightly against grabbing a whole document. It also names the sibling tools it is not, so an agent can separate it from readfetch_text and readfetch_scrape without opening a 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 gives explicit routing: 'Prefer readfetch_text for full articles; readfetch_scrape when content needs JavaScript,' plus a rule for choosing between the two required-one-of parameters ('use selector when the section has no stable heading text'). There is even a recovery path when the heading is absent — retry using the returned available_headings.

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.