ReadFetch

readfetch_map

Read-only

Discover a site's crawlable surface without crawling it: parse robots.txt allow/disallow rules, collect URLs from sitemap.xml and sitemap indexes, find RSS, Atom and JSON feeds, and count internal and external links on the homepage. Use the returned URLs to plan readfetch_scrape, readfetch_batch, or readfetch_crawl — not readfetch_map again on each URL. Prefer readfetch_probe on one URL before paying for bodies.

Input Schema

Name	Required	Description
`url`	Yes	Public http(s) URL of the site to map.
`limit`	No	Maximum number of URLs to return (1-1000).
`max_bytes`	No	Abort if any single document exceeds this many bytes.
`timeout_s`	No	Total budget for the whole call in seconds; every sitemap fetch and the browser fallback share it. 95 s is the edge ceiling (Cloudflare closes at 100 s).

Output Schema

Name	Required	Description	Default
`url`	No
`host`	No
`urls`	No
`feeds`	No
`links`	No
`robots`	No
`status`	No
`sitemaps`	No
`url_count`	No
`status_code`	No
`total_found`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedOutput schema / properties / robots / properties / crawl_delay / type
```
Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedNov 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "feeds": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "host": {
+      "type": "string"
+    },
+    "links": {
+      "properties": {
+        "external": {
+          "type": "integer"
+        },
+        "internal": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "robots": {
+      "properties": {
+        "allow": {
+          "items": {},
+          "type": "array"
+        },
+        "crawl_delay": {
+          "type": "null"
+        },
+        "disallow": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sitemaps": {
+          "items": {
+            "format": "uri",
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "sitemaps": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "total_found": {
+      "type": "integer"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "url_count": {
+      "type": "integer"
+    },
+    "urls": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedNov 1, 2026

removedInput schema / properties / egress

Removed value: -{
-  "description": "Exit to leave through: `direct` (this service's own datacentre egress) or `residential` (a residential address pool, for targets that refuse datacentre addresses). Omit to use the default route.",
-  "title": "Egress",
-  "type": "string"
-}

removedInput schema / properties / egress_fallback

Removed value: -{
-  "description": "Pool to retry through once when the first attempt is refused (bot check, wall, empty extraction, origin 403/429/5xx); must differ from `egress`. Absent keeps one exit for the whole call.",
-  "title": "Egress Fallback",
-  "type": "string"
-}

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the crucial behavioral trait that this is a cheap discovery pass that does not fetch page bodies, plus the cost tradeoff versus probe/scrape. It stops short of describing output shape or pagination, but that is largely carried by the output schema.

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 sentences, front-loaded with what it does, followed by the routing decision. No filler, no restatement of the tool name or schema fields.

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 discovery tool with a full output schema and 100% parameter coverage, nothing an agent needs to call it correctly is missing: purpose, cost model, timeout constraints (in schema), and downstream tool routing are all present.

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% — all four parameters (url, limit, max_bytes, timeout_s) are documented in the schema, including the 95s edge ceiling. The description adds no additional parameter semantics, so the baseline 3 applies.

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?

Opens with a specific verb+resource+scope: "Discover a site's crawlable surface without crawling it", then enumerates exactly what is collected (robots.txt rules, sitemap/index URLs, RSS/Atom/JSON feeds, homepage link counts). This is clearly distinguishable from readfetch_scrape, readfetch_crawl and readfetch_fetch without opening any 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?

Explicitly routes the agent: feed the returned URLs into readfetch_scrape/batch/crawl, do NOT re-run readfetch_map per URL, and prefer readfetch_probe on a single URL before paying for bodies. Both the positive path and the anti-pattern are named.

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

All ReadFetch 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?