Skip to main content
Glama

read_url

Read-only

Read a public web page as clean Markdown for LLMs: title, description, canonical URL, main content as Markdown, word count and prompt-injection flags. Respects robots.txt; not charged if the page cannot be read. — $0.001 USDC per call via x402 v2 (Base or Solana).

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(s) URL of the page to read
max_charsNoOptional cap on returned Markdown length (500-100000, default 20000)

Output Schema

NameRequiredDescriptionDefault
okYes
urlNo
metaNo
statsNo
robotsNo
statusNo
markdownNo
final_urlNo
injectionNo
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real operational context beyond them: robots.txt compliance, no charge when the page cannot be read, prompt-injection flagging, and the exact per-call price and payment rails. It stops short of describing rate limits, redirect handling, or failure modes beyond billing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: the first front-loads what is read and what comes back, the second covers constraints and cost. Every clause carries information an agent would otherwise have to guess.

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 values need not be explained, yet the description still summarizes them usefully. Combined with the pricing and robots.txt policy, an agent has enough to call it correctly; only pagination and error semantics are unaddressed.

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 coverage is 100% and both parameters are fully documented in the schema, including the max_chars range and default. The description adds no syntax or format detail for url or max_chars, so the baseline 3 applies.

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 a public web page') plus the transformation applied ('as clean Markdown for LLMs') and enumerates the returned fields. This distinguishes it from metadata-oriented siblings like domain_intel and page_links, though it never names them explicitly.

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 context is implied by 'public web page' and 'Respects robots.txt', which tells the agent this is for fetchable public content only. There is no explicit when-to-use versus when-not guidance and no routing to page_links or domain_intel for other needs.

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