Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Money per actor

actor_profitability
Read-onlyIdempotent

Compare per-actor revenue, cost, profit, runs, and paying users for a calendar month, with views for top earners, losers, movers, no-revenue, and below-cost actors to spot profitability issues.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
topNo
viewNotop = most revenue; losers = actors losing money; movers = biggest change in revenue per day vs the month before; no_revenue = paying users ran it but nothing was charged; below_cost = cost per 1K results above revenue per 1K.top
actorsNoLimit to these actors (names, ids or username/name), max 10.
periodNoA calendar month (thisMonth, lastMonth, "YYYY-MM") gives every actor. Other ranges cover only named actors or your top 10 earners.thisMonth
minRunsNo

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 establish that this is a safe, idempotent, read-only, non-destructive query, so the description needn't repeat that. It adds that results are month-oriented financial aggregates, but omits anything about result caps (default 10 rows), how partial ranges restrict coverage, or the shape of the returned rows despite having no output schema.

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?

Two sentences, metric list first and view list second, with no filler or repetition of the title. The density is appropriate for a multi-metric reporting tool, though the view enumeration partially duplicates the schema enum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter financial reporting tool with no output schema and only 60% schema coverage, the description should clarify row caps, the partial-range restriction, and how minRuns affects results. It covers the metric surface and view semantics adequately but leaves the agent guessing about result volume and filtering behavior.

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?

With 60% schema coverage, the description adds real meaning by framing the whole tool around a calendar month, which clarifies the period parameter's most useful form. It also gives the movers view a definition (change in revenue per day vs the prior month). It does not explain top, minRuns, or the actors filter beyond what the schema states.

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?

The description names a specific resource (per-actor) and enumerates the exact metrics returned: revenue, cost, profit, runs, paying/free users, per-1,000-result rates, price and break-even price, scoped to a calendar month. It is clearly distinguishable from aggregate tools like revenue_summary, though it never explicitly contrasts itself with 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 view list (top, losers, movers, no_revenue, below_cost) implies which analytical question each view answers, but the description only names them and adds a parenthetical for movers; the real definitions live in the schema enum. There is no explicit guidance on when to pick this over actor_report or revenue_summary, nor any stated prerequisites.

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