Skip to main content
Glama

Get crawl status

get_crawl
Read-onlyIdempotent

Retrieve the current status and results of a web crawl using its crawl ID to monitor progress and collect crawled pages.

Instructions

Get the current status and results of a crawl.

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

Input Schema

NameRequiredDescriptionDefault
crawl_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that both status and results come back, without saying whether results are partial while running, what terminal states exist, or whether repeated polling is the expected pattern.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though that efficiency comes partly from omitting anything beyond the bare purpose.

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 the description need not explain return values, and annotations cover the safety posture. What remains missing for a status-polling tool is the lifecycle context: when to poll, what a non-terminal state looks like, and how it differs from sibling get_job.

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% for the single crawl_id parameter, and the description does not compensate by saying where that id comes from (presumably the crawl tool's response) or whether it accepts other identifiers. It only restates the resource being fetched.

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: get the current status and results of a crawl, keyed by crawl_id. It is clear what the tool returns, but it does nothing to distinguish itself from sibling get_job, which on its face also returns job/crawl status.

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?

There is no explicit when-to-use guidance, no statement that this is the polling call for a crawl started by the crawl tool, and no exclusion against get_job. The agent has to infer the workflow from the name and parameter alone.

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