doc-scraper

Overview Schema Source Related Servers Discussions Admin

list_pages

Read-onlyIdempotent

List crawled pages for a site, paginated and sorted by URL. Returns metadata only (URL, title, depth, crawled_at, content_length).

Instructions

List crawled pages for a site, paginated and sorted by URL. Returns metadata only (URL, title, depth, crawled_at, content_length). Pass any URL returned here to read_page to get its stored markdown; get_page re-fetches a URL live rather than returning the crawled copy.

Input Schema

Name	Required	Description
`offset`	No	Pagination offset, 0-based (default: 0)
`site_key`	Yes	Site key from config (use list_sites to discover available keys)
`max_results`	No	Maximum pages to return (default: 100, max: 1000; larger values are capped, 0 or less means the default)

Output Schema

Name	Required	Description
`pages`	Yes
`total`	Yes
`offset`	Yes
`message`	No	Present when the site has no crawl output yet
`returned`	Yes
`site_key`	Yes
`max_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.21.0Oct 21, 2026

changedInput schema / properties / max_results / description

Previous value: -"Maximum pages to return (default: 100, max: 1000)"New value: +"Maximum pages to return (default: 100, max: 1000; larger values are capped, 0 or less means the default)"

changedInput schema / properties / max_results / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / offset / type

Previous value: -"number"New value: +"integer"

Changed1 schema field changedv2.15.0Oct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "max_results": {
+      "type": "integer"
+    },
+    "message": {
+      "description": "Present when the site has no crawl output yet",
+      "type": "string"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "pages": {
+      "items": {
+        "properties": {
+          "content_length": {
+            "type": "integer"
+          },
+          "crawled_at": {
+            "type": "string"
+          },
+          "depth": {
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "title",
+          "depth",
+          "crawled_at",
+          "content_length"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "returned": {
+      "type": "integer"
+    },
+    "site_key": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "site_key",
+    "pages",
+    "total",
+    "offset",
+    "max_results",
+    "returned"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds behavior beyond them: results are sorted by URL, only metadata is returned (URL, title, depth, crawled_at, content_length), and the stored copy vs live fetch distinction between read_page and get_page. It doesn't discuss pagination termination or total counts, but the added context is substantial.

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 dense sentences with zero filler: purpose and return shape first, then the routing rule, then the sibling disambiguation. Every sentence earns its place and nothing is buried.

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?

An output schema exists so return values needn't be spelled out, yet the description still names the key metadata fields. For a simple, annotation-covered read tool with fully documented parameters, nothing an agent needs in order to call it correctly is missing.

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%, and the schema already documents offset, site_key provenance (list_sites), and max_results defaults/caps. The description only implies pagination ('paginated') and adds no parameter-level syntax or bounds beyond the schema, 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?

The description names a specific verb and resource ('List crawled pages for a site') plus scope details (paginated, sorted by URL) and return shape (metadata only). It also explicitly distinguishes itself from both read_page and get_page, so an agent can tell the three apart 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?

It gives explicit routing: 'Pass any URL returned here to read_page to get its stored markdown' and clarifies that 'get_page re-fetches a URL live rather than returning the crawled copy.' That's a when-to-use plus a named alternative with its selection condition.

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

Deploy Server