Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_pages

Read-onlyIdempotent

Read one page of site crawl results by crawl ID without downloading referenced files; use cursors and a smaller limit when output caps occur.

Instructions

Read one page of crawl results without downloading referenced files. On OUTPUT_LIMIT, retry the same input cursor with a smaller limit. A single-row error may retain recovery.page references; handle that page before using recovery.continuation.

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": {
      "crawlId": "<crawlId>"
    },
    "name": "nstdata_crawl_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows in this response. Reduce down to 1 on OUTPUT_LIMIT; a single row may still exceed the output cap.
crawlIdYesActual id of the existing site crawl.
afterCursorNoCopy nextCursor from a successful page read. On OUTPUT_LIMIT, keep the original input cursor. Only use recovery.continuation.nextCursor after handling recovery.page. Mutually exclusive with beforeCursor.
beforeCursorNoCopy prevCursor from a successful read, or recovery.continuation.prevCursor after handling recovery.page. On OUTPUT_LIMIT keep the original input cursor; do not combine with afterCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld, and the description adds genuinely useful behavior: no referenced files are downloaded, page-sized reads, and an error shape that may carry recovery.page/recovery.continuation references. It stops short of describing typical return content or throughput/rate characteristics, so it adds context but not full behavioral disclosure for a paginated reader.

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 short sentences, front-loaded with purpose, then failure-mode handling in priority order. No filler and no repetition of the tool name or title.

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?

For a 4-parameter paginated read with full schema coverage and no output schema, the description covers purpose, paging limits, and error recovery well. What an agent actually receives per row is only hinted at, which is the one remaining gap.

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 coverage is 100% and the schema descriptions already spell out the limit/OUTPUT_LIMIT retry rule and the cursor mutual exclusivity, so most of what the description says about parameters is restated. The only marginal addition is the sequencing rule that recovery.continuation is used only after recovery.page, which is a 3-level contribution at best.

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 one page of crawl results') plus a scoping boundary ('without downloading referenced files') that separates it from the scrape/result siblings. It does not name an alternative tool, but the scope statement is enough to identify the operation.

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 guidance: on OUTPUT_LIMIT retry the same cursor with a smaller limit, and handle recovery.page before recovery.continuation. It does not state when to prefer this over nstdata_crawl_read_result or crawl_status, leaving one routing decision to inference.

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