Skip to main content
Glama

Get crawl pages

get_crawl_pages
Read-onlyIdempotent

Page through a crawl's pages by task id (the latest attempt's unless attemptId is given). fields keeps only the named page fields (plus id, url, status, createdAt); debug adds the routing audit and trace; includeDuplicates lists the pages whose content repeated an earlier page's. With maxResults the tool follows the cursors itself and answers { items, nextCursor, hasMore, stoppedBy }.

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": {
      "id": "<id>"
    },
    "name": "get_crawl_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
debugNo
limitNo
cursorNo
fieldsNo
attemptIdNo
maxResultsNoFollow the cursors and return up to this many pages in all.
includeDuplicatesNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreNo
stoppedByNosize: the answer reached its size budget; read on from nextCursor.
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / includeDuplicates / description
      Removed value: -"List the pages whose body repeated an earlier page's too (status duplicate, markdown null). Default false."
    • changedInput schema / properties / maxResults / description
      Previous value: -"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."New value: +"Follow the cursors and return up to this many pages in all."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds substantive context beyond them: default attempt resolution, the fact that fields always retains id/url/status/createdAt, what debug injects (routing audit and trace), duplicate-page semantics, and that maxResults follows cursors internally and can stop with a stoppedBy reason. Rate limits, permission requirements, and invalid-cursor behavior are not covered.

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?

Purpose and attempt default are front-loaded, and every clause carries information with no filler. The semicolon-chained packing of five distinct behaviors into one paragraph makes it dense to parse, which slightly hurts scanability.

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 detailed, and the description still documents the maxResults response envelope (items, nextCursor, hasMore, stoppedBy). For an 8-parameter read tool it is close to complete, though limit semantics and error conditions are left unaddressed.

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 13% (just maxResults), yet the description explains fields, debug, includeDuplicates, attemptId, and cursor/maxResults interaction, which is a strong compensation. limit and id receive no explicit explanation, leaving a small 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?

The first clause gives a specific verb and resource ("Page through a crawl's pages by task id") and clarifies the attempt scoping, which separates it from get_crawl and get_crawl_errors. It stops short of naming those siblings explicitly, so an agent must infer the boundary rather than read it.

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?

The description sets clear usage context: default is the latest attempt unless attemptId is given, and there are two distinct paging modes (manual cursor vs maxResults auto-following). No explicit when-not or sibling routing is stated, but the mode guidance is genuinely useful for selecting an invocation style.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.