Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Views to runs to paying users

growth
Read-onlyIdempotent

Analyze monthly per-actor performance to compare paying users, usage, and view-to-run conversion and identify actors needing attention.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
byNoWhich actors to show when no `actor` is given: most paying users, most 30-day users, or lowest view-to-run conversion among your 10 most-used actors.payingUsers
topNo
actorNoOne actor: adds its top referrers and countries.
monthNoCalendar month. lastMonth (default) is complete; thisMonth is in progress.lastMonth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/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 behavior, so the safety profile is covered. The description adds that a single-actor request enriches output with top referrers and countries, but that same fact is repeated in the schema, and nothing is said about data freshness, result size, or empty-data behavior.

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?

Dense and front-loaded: scope first, ranking modes in parentheses, then the enrichment note and the redirect to a sibling. The colon-led opening is slightly telegraphic but no sentence is wasted.

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 carry the return shape (per-actor funnel counts, optional referrers/countries) and the default month behavior, which is enough to call it correctly. Minor gaps remain around `top` and result ordering beyond the ranking mode.

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?

The description paraphrases the `by` enum and the `actor` and `month` semantics, but these are already documented in the schema at 75% coverage. The `top` parameter (default 5, max 10) is never explained in either place, leaving the ranking size ambiguous.

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 analytical output: view → run → pay funnel counts per actor for a calendar month, plus the three ranking modes. An agent can distinguish this reporting tool from siblings just from the sentence.

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?

Explicitly routes to acquisition_score for the 'which actors need attention and what to do' question, giving a clear alternative with a condition. It does not address other plausible alternatives (actor_report, revenue_summary), so it stops short of full when/when-not coverage.

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