Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Run health

run_health
Read-onlyIdempotent

Finds Apify actors needing attention by reporting flagged, failing, no-revenue, and revenue-at-risk status, plus failure trends and optional single-actor diagnostics.

Instructions

Finds actors that need attention: flagged (Apify notice such as under maintenance, hidden from Store search), failing (3+ failed or timed-out users' runs and 5%+ failure rate in 30 days, aborts excluded) and, with a Console session, no_revenue plus revenue at risk. Returns only problems by default, worst first. Pass actor to check one actor. Pass period (needs the Console session) for byDay: failed, timed-out and aborted runs per UTC day, today included; with actor also the failed runs users shared with you, their log tails, recent builds and the build before the failures began.

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": "run_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
logsNoWith `actor` and `period`: include the last 30 log lines of up to 3 newest failed shared runs.
actorNoOne actor (id, name, username/name or title). Omit to check every actor.
periodNoAdd `byDay`: failed / timed-out / aborted runs per UTC day for this period, today included (partial). With `actor`, also the failed runs users shared with you, their log tails and recent builds. Needs the Console session. today | yesterday | last7d | last30d (both end yesterday) | thisMonth | lastMonth | "YYYY-MM" | {from, to} (YYYY-MM-DD, max 12 months)
onlyProblemsNoReturn only actors with a flag. Ignored when `actor` is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.3/5.0
Behavior4/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 is covered; the description adds real context beyond that: the Console-session requirement for `no_revenue`/`period`, the detection thresholds, and the default ordering ('worst first'). It stops short of describing pagination limits or the precise response shape, so it is strong but not exhaustive.

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-loaded with the core outcome (actors needing attention) before the mode/parameter caveats, and every clause carries substantive detail. The final sentence is long and clause-heavy, packing `byDay` plus shared-run/build behavior together, which costs some scannability.

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 five parameters and no output schema, the description does the necessary work of explaining what each mode returns (problem categories, per-UTC-day run counts, log tails, recent builds) and the session prerequisite. Minor gaps remain around result ordering beyond 'worst first' and how `top` interacts with the `actor` case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so much is already documented, yet the description adds cross-parameter interaction and precondition meaning: `period` adds `byDay` and needs the Console session, `logs` only applies with `actor` plus `period`, and `actor` also unlocks shared-run log tails and build history. The `top` parameter is the one item left entirely to the schema.

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 and resource ('Finds actors that need attention') and enumerates the exact categories it returns (flagged, failing, no_revenue) with concrete thresholds like '3+ failed or timed-out users' runs and 5%+ failure rate in 30 days'. This is clearly a diagnostic/health-check tool, distinguishable from inventory-style siblings such as list_actors or actor_report without opening the schema.

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?

Gives concrete operating guidance: 'Returns only problems by default', 'Pass `actor` to check one actor', 'Pass `period` (needs the Console session) for `byDay`'. It explains how to narrow scope and what triggers extra data, but never states when to prefer a different tool or when this tool is the wrong choice.

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