alterlab-mcp-server

Get Crawl Status

alterlab_crawl_status

Read-onlyIdempotent

Poll an ongoing or completed crawl to check progress and retrieve scraped page content after starting the crawl.

Instructions

Poll the status and results of an ongoing or completed crawl. Call this after alterlab_crawl to check progress and retrieve scraped pages. Status values: queued, running, completed, failed, cancelled. When completed, results contains the scraped page content.

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": {
      "crawl_id": "<crawl_id>"
    },
    "name": "alterlab_crawl_status"
  }
}

Input Schema

Name	Required	Description	Default
`crawl_id`	Yes	Crawl ID returned by alterlab_crawl

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jun 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds genuine behavioral context beyond them: the closed set of status values (queued, running, completed, failed, cancelled) and the fact that results only carries page content once completed. It does not mention polling intervals or result truncation, keeping it below a 5.

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 call-site guidance, then the status vocabulary. Every sentence carries information an agent would otherwise have to infer; nothing is redundant.

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 simple single-parameter polling tool with no output schema, the description covers the essentials: the state machine and where results appear. It leaves open whether results are paginated or how long completed results persist, which are minor but real gaps for a polling loop.

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 single parameter is documented as 'Crawl ID returned by alterlab_crawl', which the description echoes without adding format, source, or reuse details. With one fully documented parameter, baseline 3 is appropriate.

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 ('Poll') and resource ('status and results of an ongoing or completed crawl'), and ties itself to alterlab_crawl as the originating call. An agent can tell this is the read-side companion to the crawl starter. It stops short of distinguishing itself from sibling pollers like alterlab_get_job or alterlab_batch_status, which a 5 would require.

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?

'Call this after alterlab_crawl to check progress and retrieve scraped pages' gives explicit sequencing and the triggering condition. There is no guidance on when-not to use it (e.g., versus alterlab_get_job) or how frequently to poll, so it is clear context without alternatives.

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