Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

List my actors

list_actors
Read-onlyIdempotent

Retrieve actors in a connected Apify account with 7/30-day user counts, 30-day run and failure rates, last run, and notices; search by name or filter by visibility.

Instructions

The connected account's actors with users (7/30 days), users' runs and failure rate (30 days), last run and any Apify notice. Default: top 25 by 30-day users. Use query to find an actor by name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_actors"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
sortNousers30d
queryNoOnly actors whose name or title contains this text.
visibilityNoall
onlyWithNoticeNoOnly actors Apify has put a notice on (e.g. under maintenance).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restating. Beyond that the description usefully discloses the returned metric set, the 30-day default window and the 25-item default cap, but says nothing about total counts, pagination beyond `top`, or what happens when the account has no actors.

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?

Three sentences, front-loaded with what is returned, then defaults, then the lookup hint. Dense but every clause carries information; the metrics parenthetical is compact without being cryptic.

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 no output schema, the description does the work of describing the return payload, which is the main gap it needs to fill, and it also pins down default ordering and size. What remains missing is minor: semantics of `visibility`/`onlyWithNotice` and whether results are paginated or truncated at `top`.

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 only 40%, so the description meaningfully covers `query` (name or title substring), `top` (25 default) and `sort` (30-day users). `visibility` and `onlyWithNotice` are only glancingly referenced ('any Apify notice'), leaving their effect on results undocumented in both schema and prose.

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?

Names the specific resource (the connected account's actors) and enumerates the metrics returned: users 7/30 days, runs, failure rate, last run, Apify notice. The verb is implicit from the name rather than stated, and nothing distinguishes it from analytics siblings like actor_report or actor_quality.

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 only real guidance is 'Use `query` to find an actor by name', which is sub-task guidance within the tool rather than guidance on when to pick this over a sibling. Usage is implied by the listing scope and the stated default (top 25 by 30-day users), but no exclusions or alternatives are given.

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