Skip to main content
Glama
apify

actors-mcp-server

Official
by apify

Abort Actor run

abort-actor-run
DestructiveIdempotent

Stop a running or starting Actor run. Use when a run is taking too long or misconfigured.

Instructions

Abort an Actor run that is currently starting or running. For runs with status FINISHED, FAILED, ABORTING, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.

USAGE:

  • Use when you need to stop a run that is taking too long or misconfigured.

USAGE EXAMPLES:

  • user_input: Abort run y2h7sK3Wc

  • user_input: Gracefully abort run y2h7sK3Wc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesThe ID of the Actor run to abort.
gracefullyNoIf true, the Actor run will abort gracefully with a 30-second timeout.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesActor run ID
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions
actorIdYesStable Apify Actor ID from the run record
actorNameNo"username/actor-name"
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
statusMessageNoPass-through from Apify run.statusMessage
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statsNoRun statistics
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
summaryYesPast-tense summary of the run state
nextStepYesOne primary follow-up action with identifiers interpolated
Behavior5/5

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

The description reveals behavioral details beyond annotations, such as that graceful abort uses a 30-second timeout, the effect is idempotent, and the results include updated run details. These align with annotations (destructiveHint=true, idempotentHint=true) without contradiction.

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?

The description is concise and well-structured, using clear sections (USAGE, USAGE EXAMPLES). Every sentence adds value without redundancy, and the examples are helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown but indicated) and the comprehensive description covering behavior, idempotency, graceful abort, and status conditions, the description is complete enough for an agent to use the tool 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?

The input schema already has 100% coverage with clear descriptions for both parameters (runId and gracefully). The description does not add new meaning beyond the schema's own descriptions, so it meets the baseline but does not exceed it.

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 clearly states the tool's purpose: 'Abort an Actor run that is currently starting or running.' It also specifies conditions where it has no effect (FINISHED, FAILED, ABORTING, TIMED-OUT), which distinguishes it from sibling tools like get-actor-run or call-actor.

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

Usage Guidelines5/5

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

The description includes explicit usage guidance: 'Use when you need to stop a run that is taking too long or misconfigured.' It also provides concrete usage examples showing how to invoke the tool, making it clear when to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/apify/apify-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server