openactors

Abort Actor run

abort-actor-run

Cancel an ongoing actor run and keep data already collected. Use it to stop a scraper that is still in progress without losing the items gathered so far.

Instructions

Stop a run that is still in progress. Items already collected are kept.

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": {
      "runId": "<runId>"
    },
    "name": "abort-actor-run"
  }
}

Input Schema

Name	Required	Description	Default
`runId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the responsibility for behavioral disclosure. It does this well by stating both the precondition ('still in progress') and the key side effect ('Items already collected are kept'). It doesn't cover every edge case such as idempotence or the terminal run status, but the most decision-relevant behavior is disclosed.

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?

Two short sentences with no filler. The action is front-loaded, and the critical side effect about preserving collected items is stated immediately.

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 tool with no output schema, the description covers the essential action, precondition, and consequence. It could be more complete by noting what happens when the run is not in progress or whether the abort is final, but those are minor gaps for this simple operation.

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?

The schema provides only a required string runId with no description, and the description doesn't explicitly define runId. However, the tool name and the phrase 'a run' make it inferable that runId identifies the run to abort, so the parameter is usable but not directly enriched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Stop') and resource ('a run that is still in progress'), making the tool's purpose unmistakable. It also distinguishes itself from read-only siblings like get-actor-run and from the opposite operation resurrect-actor-run.

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?

The description clearly conveys when to use the tool: when a run is in progress and needs to be stopped. It doesn't explicitly name alternatives or exclusions, but the 'still in progress' precondition provides enough context to avoid most misuse.

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