Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

research_cancel

Cancel a running research job by job ID, returning its cancellation state, progress counts, and usage. Retained results stay readable and are marked partial.

Instructions

Cancel a research job. Requests cancellation of the caller's own research job, given by job_id. Returns the job's current state (such as cancelling), cancel_requested, partial, progress counts, research progress and usage. Results already retained stay readable and are marked partial where appropriate.

Input Schema

NameRequiredDescriptionDefault
job_idYesResearch job ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It explains that cancellation is requested asynchronously, that the response includes states such as cancelling, cancel_requested, partial, and progress counts, and that retained results stay readable and may be marked partial.

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?

The description is three tight sentences. It leads with the action, then the ownership constraint, then the response behavior. Nothing is wasted, though the state-field list is slightly dense.

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 one-parameter mutation tool with no output schema and no annotations, the description covers the essential return state, partial-result behavior, and ownership scope. It is missing error or invalid-job behavior, but it is otherwise sufficient to call correctly.

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%, so job_id is already documented as a research job ID. The description adds the ownership constraint that it must be the caller's own job, but it does not add format, sourcing, or lookup guidance beyond the schema.

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 names a specific verb and resource: cancel a research job. It also narrows scope to the caller's own job. It does not explicitly contrast with siblings like research_status, but the action is unambiguous.

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?

The required job_id and ownership constraint imply when to use it. However, the description does not say when not to cancel, nor does it point to research_status or research_results as alternatives for non-cancellation workflows.

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

Deploy Server

Other Tools