Agent Toolbox

Url To Markdown

url_to_markdown

Read-only

Fetch a public web page or document (HTML, PDF, Word, Excel, CSV, XML; up to 10 MB) and return it as clean Markdown with its title and final URL. Add render=true for pages that build their content with JavaScript: they are opened in a real headless Chrome first. Costs USD 0.002 per call, paid with x402 (USDC on Base); calls that fail are not charged.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	A public http(s) URL
`render`	No	Open the page in a real headless Chrome first, for pages built with JavaScript (slower; default false)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / render

Added value: +{
+  "description": "Open the page in a real headless Chrome first, for pages built with JavaScript (slower; default false)",
+  "type": "boolean"
+}

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond annotations: supported input formats, a 10 MB size cap, x402/USDC-on-Base pricing at USD 0.002 per call, and the fact that failed calls are not charged. These are material operational details an agent needs before invoking an open-world paid fetch.

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?

Three tightly packed sentences. Core behavior, optional render path, and pricing/failure policy are front-loaded with no filler or repetition.

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?

With no output schema, the description still explains that the result is clean Markdown plus title and final URL. Size limits, formats, pricing, failure billing, and the JavaScript rendering option together cover what an agent needs to call the tool correctly.

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 the baseline is 3; the description earns an extra point by adding meaningful render semantics: JavaScript-built pages are opened in real headless Chrome, and this path is slower. The URL constraint is also restated as public http(s), reinforcing the schema.

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: fetch a public web page or document and return it as clean Markdown with title and final URL. Supported formats and size limit add precision. It does not explicitly distinguish itself from siblings like read_url or file_to_markdown, so it lands just short of a 5.

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?

Gives clear conditional guidance: use render=true for JavaScript-built pages, with the tradeoff noted as slower and default false. However, it does not name or exclude alternative tools such as read_url, leaving sibling selection to inference.

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

All Agent Toolbox tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?