Skip to main content
Glama

Read URL

read_url

Read a public http(s) URL as markdown. Uses text/markdown when the server sends it, otherwise Workers AI toMarkdown with images off (no neurons), then a local HTML stripper. Respects robots.txt for BotThruFetcher. Does not cache or store the page.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http or https URL. No private addresses, no credentials.
max_charsNoMaximum characters of markdown. Default 20000, maximum 100000.

Output Schema

NameRequiredDescriptionDefault
okNo
errorNo
titleNo
statusNo
markdownNo
final_urlNo
truncatedNo
content_typeNo
approx_tokensNo
content_signalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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 well: it discloses the conversion pipeline (server markdown, then Workers AI toMarkdown with images off, then a local HTML stripper), robots.txt enforcement, and that nothing is cached or stored. Those are real operational facts an agent needs (e.g., robots-blocked pages will fail, images will be absent). It stops short of stating error/redirect/rate-limit behavior.

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?

Four short sentences, front-loaded with the core capability and then the mechanics. No filler or marketing language. Minor jargon ('BotThruFetcher', 'neurons') costs a little clarity but is used to convey cost/behavior tradeoffs, not decorate.

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?

An output schema exists, so return-value description is unnecessary, and the description correctly focuses on how the content is produced and on the no-cache guarantee. For a two-parameter read tool this is close to sufficient; failure modes (robots denial, non-HTML content, network errors) are the remaining gap.

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 both `url` and `max_chars` are already documented, including the default and the 100000 ceiling. The description adds nothing parameter-specific — it doesn't explain what happens when max_chars truncates or how that interacts with the AI conversion path. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource+output form: 'Read a public http(s) URL as markdown.' That is enough for an agent to know exactly what comes back. It does not, however, differentiate itself from likely-overlapping siblings such as fetch_page or check_url, so the agent must infer which one to call.

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?

Usage is only implied: it is the tool for pulling a public page's content as markdown. There is no explicit when-to-use / when-not-to-use and no named alternative (fetch_page is an obvious candidate for differentiation). The 'public http(s) URL' scoping is the only implicit boundary, and that constraint is already in the schema.

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