Skip to main content
Glama
spidra-mcp-server

spidra-mcp-server

Official
by spidra-io

spidra_crawl_pages

Read-only

Read a crawl's pages in order with pagination to retrieve results beyond the first 100 pages or recover pages from a cancelled crawl, including Markdown and HTML links.

Instructions

Read a crawl's pages, in order, with each page's data and links to its Markdown and HTML (the links last 1 hour). Use it for crawls of more than 100 pages, since spidra_get_job returns only the first 100, or after a cancelled crawl to get the pages it finished.

Page through with "offset" and "limit" until "hasMore" is false. Keep "limit" small (20 to 50) to save context. Each page's "id" is what spidra_retry_crawl_page needs.

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": {
      "jobId": "<jobId>"
    },
    "name": "spidra_crawl_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe crawl's jobId
limitNoPages to return (default 50 here)
offsetNoPages to skip (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / jobId / description
      Added value: +"The crawl's jobId"
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Pages to return (default 50 here)",
      +  "maximum": 1000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Pages to skip (default 0)",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observedv0.2.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations provide the necessary safety context (readOnlyHint: true). The description adds crucial behavioral details, specifically that the returned links are only valid for 1 hour, which informs the agent about data freshness.

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?

The description is highly dense and efficient. It logically moves from the core purpose to the operational use case, the technical implementation pattern, and the required external dependency (spidra_retry_crawl_page).

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?

The description is exceptionally complete for this level of tool. It explains the necessary loop (offset/limit) and provides the context for the subsequent step of the workflow—that the returned page ID is required by spidra_retry_crawl_page.

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?

Although schema coverage is 100%, the description adds significant value by providing operational advice regarding the 'limit' parameter, instructing the agent to keep it small to prevent context overload.

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 clearly defines the tool as reading pages from an existing crawl. It differentiates itself by stating its specific use cases: crawls over 100 pages, or after a cancellation, which distinguishes it from tools like spidra_get_job.

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?

The description outlines a clear workflow: use 'offset' and 'limit' to page through results until 'hasMore' is false. It also dictates operational constraints, specifically recommending a small 'limit' (20-50) to save context.

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