Skip to main content
Glama

Read Crawl Job

crawl_status
Read-only

Read a crawl job's checkpoint with paginated results to inspect progress or loss; checkpoints from lost jobs do not imply the crawl can be resumed.

Instructions

Read a Crawl Job checkpoint with page pagination. Lost jobs expose checkpoints but never imply resumable execution.

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": "crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
crawlIdYes
maxCharsPerPageNo

Output Schema

NameRequiredDescriptionDefault
pagesYes
totalYes
errorsYes
offsetYes
statusYes
crawlIdYes
hasMoreYes
partialYes
returnedYes
completedYes
expiresAtNo
artifactIdNo
providerJobIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish that this is read-only and not open-world. The description adds useful behavioral context by mentioning pagination and clarifying that checkpoints from lost jobs are exposed without implying resumability; the remaining gaps around auth or rate limits are less critical given the annotations.

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 definition is two sentences, front-loaded with the core read operation and followed by a relevant caveat. There is no wasted wording or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value details need not be explained, and annotations cover the safety profile. However, with four parameters at 0% description coverage, the definition is only minimally complete for constructing calls, especially regarding maxCharsPerPage and pagination semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only mentions 'page pagination' without explaining crawlId, limit, offset, or maxCharsPerPage. This provides minimal help beyond the raw schema types and constraints.

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 description states a specific verb and resource: 'Read a Crawl Job checkpoint,' and adds that pagination applies. It is clear enough to distinguish this from job-launching or cancellation tools, though it does not explicitly compare itself to siblings such as crawl or crawl_cancel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage-adjacent statement is the caveat that lost jobs expose checkpoints but do not imply resumable execution. There is no explicit guidance on when to call this instead of crawl, crawl_cancel, or other job-related tools, so the agent must infer the intended context.

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