Skip to main content
Glama
apify

actors-mcp-server

Official
by apify
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Actor run

get-actor-run
Read-onlyIdempotent

Check the status and details of an Actor run. Optionally wait for the run to reach a terminal state.

Instructions

Get detailed information about a specific Actor run.

Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.

  • summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").

  • nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").

  • waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.

USAGE:

  • Use to check the status of a run started with call-actor.

  • Pass waitSecs > 0 to block until terminal (or until the cap elapses).

  • If call-actor-widget or get-actor-run-widget rendered a widget for this run, do NOT poll here — the widget self-polls.

USAGE EXAMPLES:

  • user_input: Show details of run y2h7sK3Wc

  • user_input: Wait for run y2h7sK3Wc to finish

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesThe ID of the Actor run.
waitSecsNoMaximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30.

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

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds behavioral details: return fields (summary, nextStep), waitSecs blocking behavior. Does not contradict annotations. Additional context is useful but not exhaustive (e.g., no mention of rate limits).

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?

Description is well-structured with clear sections (purpose, usage, examples). Front-loaded with main purpose. Slightly verbose in examples (two lines) but overall efficient for the detail provided.

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 output schema present, description need not detail return values, but it adds helpful context about summary/nextStep. Annotations cover safety. Missing info on pagination or error codes, but adequate for core use.

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 the schema fully documents both parameters. The description adds minimal new semantic meaning beyond the schema (e.g., waitSecs blocking behavior is already in schema). Baseline 3 is appropriate.

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 retrieves detailed information about a specific Actor run, with a specific verb 'Get' and resource 'Actor run'. It distinguishes itself from siblings by referencing related tools like call-actor and widget self-polling, providing clear differentiation.

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?

Explicitly states when to use (check status, wait for terminal) and when not to poll (if widget self-polls). Provides usage examples and integrates with sibling tool call-actor, offering clear context and exclusions.

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