Octocrawl

Get crawl pages

get_crawl_pages

Read-onlyIdempotent

Retrieve paginated crawl page results by task ID. Follow cursors up to maxResults, include duplicates or debug data, and continue from nextCursor.

Instructions

Read a paginated list of crawl page results by task id (the latest attempt's unless attemptId is given). Pages omit the routing audit and trace unless debug is true, and leave out pages whose content repeated an earlier page's (status duplicate) unless includeDuplicates is true. With maxResults the tool follows cursors itself, up to that many pages, and answers { items, nextCursor, hasMore, stoppedBy }.

Input Schema

Name	Required	Description
`id`	Yes
`debug`	No
`limit`	No
`cursor`	No
`attemptId`	No
`maxResults`	No	Follow cursors from cursor on and return up to this many pages in all, each request no larger than what is still wanted; nextCursor then continues exactly after the last page returned, and stoppedBy says whether the end or this cap stopped the listing.
`includeDuplicates`	No	List the pages whose body repeated an earlier page's too (status duplicate, markdown null). Default false.

Output Schema

Name	Required	Description
`items`	Yes
`hasMore`	No
`stoppedBy`	No	size: the answer reached its size budget; read on from nextCursor.
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Oct 18, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: default omission of routing audit/trace, default suppression of status-duplicate pages, automatic cursor following when maxResults is set, and the exact response envelope. Annotations cover the safety profile while the description covers the data-shaping behavior, which is exactly the split needed here.

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?

Tight and front-loaded: purpose first, then two conditional filters, then the pagination mode. Every clause carries information, though the final sentences are densely packed with nested conditions that a reader must parse carefully.

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?

Covers the operation, its default filters, pagination semantics, and the key response fields even though an output schema exists. The one residual gap is how limit and maxResults relate when both are supplied, which matters for a 7-parameter paging tool.

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 description coverage is only 29%, so the description carries most of the load: it explains the attemptId default, the debug and includeDuplicates filters, and the maxResults cursor-following semantics including stoppedBy. It leaves 'limit' vs 'maxResults' interaction and 'cursor' unexplained, so it doesn't fully close the coverage gap.

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 paginated list of crawl page results by task id'. The scoping detail ('the latest attempt's unless attemptId is given') makes it distinguishable from get_crawl and get_crawl_errors. It never names a sibling explicitly, so differentiation is inferred from the resource rather than stated.

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 concrete conditional usage for three flags: debug is needed to see routing audit and trace, includeDuplicates is needed to see repeated-content pages, and maxResults switches the tool into self-following cursor mode. There is no explicit when-not or named-alternative guidance, but the default behavior of each option is clear.

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