Apify MCP Server

Get user Actors list

get-actor-list

Read-onlyIdempotent

List Actors owned by or shared with your Apify account, including private ones, to find names for running or inspecting them. Returns summaries with pagination and sorting.

Instructions

List the Actors of the authenticated account: the ones it owns and the ones shared with it, private ones included. Returns summaries only (id, fullName, title, dates) — use fetch-actor-details with a fullName from the list for the input schema and README. search-actors searches Apify Store instead and never returns private Actors. Sorted by createdAt (newest first by default); use limit (max 20), offset, and desc to paginate and sort.

USAGE:

Use when you need to know which Actors the account has, for example to find the name of one to run or inspect.

USAGE EXAMPLES:

user_input: List my Actors
user_input: Which Actors did I create most recently?
user_input: Show my oldest Actors

Input Schema

TableJSON Schema

Name	Required	Description
`desc`	No	If true, the Actors are sorted by createdAt, newest first. Default is true; false lists oldest first.
`limit`	No	Maximum number of Actors to return. Default is 10. Maximum is 20.
`offset`	No	Number of Actors to skip at the start of the list. Default is 0.

Output Schema

TableJSON Schema

Name	Required	Description
`desc`	No	Whether items are sorted in descending order.
`count`	Yes	Number of items returned in this page.
`items`	Yes	Actors.
`limit`	Yes	Maximum number of items requested.
`total`	Yes	Total number of items across all pages.
`offset`	Yes	Number of items skipped from the start.
`summary`	Yes	Summary of the result
`nextStep`	Yes	One follow-up action with tool name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.17.0Oct 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive), so the bar is low; the description still adds real value by disclosing that only summaries are returned (id, fullName, title, dates), the sort default, the hard limit of 20, and the private-Actor inclusion rule. No contradictions.

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?

Front-loads the core purpose, then routing and pagination details in descending priority. The USAGE/USAGE EXAMPLES blocks are somewhat redundant with the first paragraph, but every line still carries actionable routing or pagination information.

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?

An output schema exists, so return values needed no explanation, yet the description helpfully characterizes the payload as summaries. Combined with the sibling routing, pagination rules, and privacy note, an agent has everything needed to call this 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 description coverage is 100%, so desc, limit, and offset are fully documented in the schema already. The description largely restates those same semantics (newest-first default, max 20) without adding syntax or edge-case meaning beyond the schema, which is the expected baseline.

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?

States a specific verb+resource ('List the Actors of the authenticated account') and precisely scopes it — owned plus shared, private included. It explicitly distinguishes itself from two siblings (fetch-actor-details for schemas, search-actors for the Store), so an agent can pick correctly without opening a schema.

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?

Gives an explicit when-to-use condition ('when you need to know which Actors the account has... to find the name of one to run or inspect') plus two named alternatives with their exclusion conditions. The user_input examples reinforce the trigger phrases.

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

Deploy Server