AgentIndex x402

Web Page to Markdown

read_web_page

Read-onlyIdempotent

Fetch URL content as Markdown: read any web page and get clean Markdown - navigation, ads and boilerplate stripped, links resolved, plus a real token count. The same extraction /search uses on result pages, exposed standalone for a URL you already have. Try GET /web-read/sample. Part of the AgentIndex content kit (pdf, web-read, extract, summarize, detect-language) - see GET /capabilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	URL of the page to read.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`title`	No	Page title, when found.
`markdown`	Yes	Main article content as clean markdown - navigation, ads and boilerplate removed, links resolved.
`token_count`	Yes	Real BPE token count (cl100k_base) of the markdown.
`x402_receipt`	No	Billing and provenance receipt for this call.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / url / description
```
Added value: +"URL of the page to read."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "markdown": {
+      "description": "Main article content as clean markdown - navigation, ads and boilerplate removed, links resolved.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Page title, when found."
+    },
+    "token_count": {
+      "description": "Real BPE token count (cl100k_base) of the markdown.",
+      "type": "integer"
+    },
+    "url": {
+      "type": "string"
+    },
+    "x402_receipt": {
+      "description": "Billing and provenance receipt for this call.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "url",
+    "markdown",
+    "token_count"
+  ],
+  "type": "object"
+}

AddedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds real behavioral value beyond that: what gets stripped, that links are resolved, and that a token count is returned. It does not discuss failure modes (paywalls, timeouts) but the extra context is substantive.

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-loads the core verb and output transformation before mentioning the sample endpoint and the content-kit promotion. The trailing links to 'GET /web-read/sample' and 'GET /capabilities' are slightly promotional but cheap and potentially useful, so only minor waste.

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, and the description covers behavior, scope, and a sample endpoint. For a single-parameter read tool it is essentially complete; only failure/limit behavior is 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?

One parameter at 100% schema description coverage, so the schema already documents 'url' fully. The description adds no syntax, format, or edge-case guidance for the URL beyond what the schema provides, making the baseline 3 appropriate.

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+resource ('Fetch URL content as Markdown') and immediately qualifies the output ('navigation, ads and boilerplate stripped, links resolved, plus a real token count'). It also distinguishes itself from the sibling search tool by positioning itself as the standalone version 'for a URL you already have.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the use case against the alternative: 'The same extraction /search uses on result pages, exposed standalone for a URL you already have.' This tells the agent when to pick this over search, though it does not state exclusions (e.g. PDFs go to read_pdf) or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentIndex x402 tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.