apify-insights
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Answers questions about the Apify actors owned by the connected account: money, users, run health, notices, pricing, Store rank. "How am I doing" → daily_brief. "Is anything broken" → run_health. "On which days did runs fail, how many today, which runs failed and why" → run_health with period (add actor for the failed runs, log tails and builds). "Which actors lose money / should I reprice" → actor_profitability(view: losers) then actor_report. "How many viewed, ran or paid", referrers, countries → growth. "Which actors are leaking, rising or fading, and what to do" → acquisition_score. "What should I fix for quality" → actor_quality. Read apify-insights://glossary before explaining a metric. Repeat numbers exactly as returned; null means "not available", never zero; never estimate. Per-actor money is paying-users money by calendar month; day ranges per actor cover only named actors or the top 10 earners.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Whether the Apify API token works (and for which account) and the state of the Console session used for money data. Call this when another tool returns an auth error. |
| daily_briefA | Yesterday and month-to-date money (paying users) vs the same days last month, plus up to three actors to look at, each with the rule that flagged it and the next call to make. Falls back to health only without a Console session. |
| revenue_summaryA | Account revenue, cost, profit and margin for any period (yesterday, last7d, a month, a date range), optionally compared with the previous period or the same days last month. |
| actor_profitabilityA | Per-actor revenue, cost, profit, runs, paying/free users, cost and revenue per 1,000 results, price and break-even price for a calendar month. Views: top, losers, movers (change in revenue per day vs the month before), no_revenue, below_cost. |
| run_healthA | Finds actors that need attention: |
| actor_reportA | Everything known about one actor: users, 30-day run results, flags, current price, default memory and timeout, latest build, reviews, local source folder, and (with a Console session) the last three months of money with unit costs and break-even price. |
| list_actorsA | 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 |
| growthA | For a calendar month: how many users viewed your actors, ran them and paid, per actor (most paying users, most used, or worst view-to-run conversion). One actor adds top referrers and countries. For which actors need attention and what to do, use acquisition_score. |
| acquisition_scoreA | Which actors need attention for acquisition, and what to do: each of your top actors (by 30-day users) is Leaking, Rising, Fading, Converting, Steady or Quiet, judged against the same point last month and against your other actors, with the reason. Rising and Fading are not judged before day 8 of the month. Pass |
| actor_qualityA | Apify's quality score for your actors and its improvement suggestions, grouped by work type (security, operations, schema, pricing, listing) and ranked by impact (work-type weight × traffic). Without |
| store_rankB | Your actors' positions in Apify Store search for up to 10 keywords, in the order a Store visitor sees, with the actors ranked above your best one. |
| competitor_benchmarkB | Your public portfolio vs another creator's: actors, users (30 days), median users per actor, actors with 10+ and 100+ users, total runs, and each side's top 5 actors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| morning-brief | How the Apify portfolio is doing today and what to look at. |
| loss-hunt | Which actors lose money or charge nothing, and why. |
| health-check | Which actors are flagged, failing or charging nothing. |
| funnel-check | Which actors are gaining or losing users, and what to do. |
| quality-review | Which quality suggestions to fix first across your actors. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| glossary | What each number returned by this server means. |
TDQS
Scored across 12 tools
Most tools target a distinct analysis axis (money, health, quality, acquisition, search rank, competition), and descriptions explicitly disambiguate the risky pairs, e.g. growth vs acquisition_score ('same numbers and field names as growth; for raw counts... use growth') and revenue_summary vs daily_brief. There is still a cluster of four tools answering 'which actors need attention' (run_health, actor_quality, acquisition_score, daily_brief) that an agent could plausibly misselect, though the rule sets differ enough to be workable.
All names are snake_case and readable, but conventions differ: verb_noun (list_actors), noun_noun (auth_status, revenue_summary, run_health, actor_report), and bare noun phrases (growth, store_rank, competitor_benchmark). The actor_ prefix is used for some actor-scoped tools but not others (actor_profitability vs growth), so the namespace is inconsistent.
Twelve tools is squarely in the well-scoped range, and each maps to a coherent analytics question (one actor, all actors, money, health, quality, rank, competitor) rather than redundant variants. Nothing feels padded.
The analytics domain is well covered end-to-end: auth, portfolio listing, per-actor deep dive, revenue/cost/margin, run health, quality, acquisition, store rank, and benchmarking, spanning both overview and drill-down. Minor gaps remain around longitudinal trending/export of metrics and explicit remediation or alerting actions, but agents can work around these via period parameters and date ranges.