Crawlora MCP

web_crawl_cancel

Idempotent

Return the current crawl job state after requesting cooperative cancellation. Pass an owned job ID; retained results remain available and settlement proceeds asynchronously.

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": {
      "job_id": "<job_id>"
    },
    "name": "web_crawl_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	required,Owned crawl job ID returned by web_crawl_submit.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare idempotentHint/destructiveHint/openWorldHint, and the description usefully adds that cancellation is cooperative, retained results stay available, and settlement is asynchronous. These are genuine behavioral facts beyond the annotation set. It does not discuss behavior for already-finished or non-cancellable jobs, keeping it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and result. The second sentence packs ownership, result retention, and async settlement with no filler, though the density borders on terse.

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?

With an output schema present, return values need not be described, and annotations carry the safety profile; the description covers ownership, retention, and async settlement. Only edge-case behavior for un-cancellable jobs is absent, a minor 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?

At 100% schema coverage, the schema already documents job_id including its ownership and origin. The description's 'owned job ID' restates the schema rather than adding syntax or format detail, so the 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?

The description states a specific action ('requesting cooperative cancellation') and resource ('crawl job'), with the return value ('current crawl job state') also named. It is distinguishable from most siblings by the cancellation semantics, though it does not explicitly contrast with web_crawl_status, which superficially reads the same way.

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

Usage Guidelines3/5

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

'Pass an owned job ID' gives a precondition (ownership) but there is no explicit when-to-use/when-not guidance and no named alternative. An agent must infer that this is the tool for stopping a crawl rather than web_crawl_status.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?