Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Acquisition triage

acquisition_score
Read-onlyIdempotent

Identify which top Apify actors need acquisition attention and why, classifying each as Leaking, Rising, Fading, Converting, Steady, or Quiet with recommended next steps.

Instructions

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 for one actor. Same numbers and field names as growth; for raw counts, paying users, referrers or countries use growth.

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

Input Schema

NameRequiredDescriptionDefault
topNoHow many actors to scan, by 30-day users. Buckets are relative to these actors.
actorNoOne actor (id, name, username/name or title): its bucket, reason and numbers. Omit for the portfolio triage.
monthNoCalendar month. thisMonth (default) is compared with last month at the same point; a past month with the whole month before it.thisMonth

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 cover readOnly/idempotent/non-destructive/openWorld, so the description's job is semantics – and it delivers: buckets are judged against the same point last month and against peer actors, the day-8 suppression rule is disclosed, and it points to growth for compatible output field names. Missing only what the response payload looks like in its own right (no output schema), which keeps it off a 5.

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 question it answers, then the rules, then the handoff to growth. Dense but every clause carries information (buckets, comparison basis, day-8 caveat, actor toggle, growth fallback); the semicolon-comma packing is slightly heavy but not padded.

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?

For a 3-optional-param read tool with no output schema, the description covers purpose, selection logic, timing caveats and an output-shape cross-reference. The only remaining gap is that the actual numbers/fields returned are delegated to the growth tool rather than described here.

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 100%, so the baseline is 3; the description earns an extra point by explaining the consequence of `top` (buckets are relative to the scanned set) and the portfolio-vs-single-actor meaning of omitting `actor`. The `month` comparison semantics are largely already in the schema, so it adds only marginal value there.

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 question it answers ("which actors need attention for acquisition") plus the enumeration of buckets (Leaking, Rising, Fading, Converting, Steady, Quiet) and the reason field. It also explicitly distinguishes itself from the sibling growth tool for raw counts, paying users, referrers and countries, so an agent can route without reading either 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 selection rules: pass `actor` for a single actor, omit it for the portfolio triage, and use growth instead when you need raw counts or non-acquisition dimensions. A conditional exclusion is also stated (Rising/Fading not judged before day 8). It stops short of naming every adjacent sibling (e.g. actor_quality, revenue_summary) but the routing guidance present is unambiguous.

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