Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Quality scores and suggestions

actor_quality
Read-onlyIdempotent

Retrieve Apify quality scores, sub-scores, praises, and ranked improvement suggestions per actor or across your top actors by 30-day users to prioritize fixes by impact.

Instructions

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 actor: the top issues across your top actors by 30-day users, each with the actors it affects. With actor: that actor's score, sub-scores, praises and suggestions.

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_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many actors to scan, by 30-day users. Impact levels are relative to these actors.
actorNoOne actor (id, name, username/name or title): its score, sub-scores, what Apify praises and its suggestions. Omit for the portfolio's top issues.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive safety, and the description adds genuinely new behavior: impact is computed as work-type weight × traffic, and results are scoped to a 30-day-user-ranked cohort. It does not discuss cost, latency, or auth for a read-only portfolio scan, so it stops short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the resource and ranking logic, then the mode split. No filler, no restatement of the tool name.

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 describe the shape of both return modes (top issues with affected actors; per-actor score, sub-scores, praises, suggestions). Reasonably complete for a read-only two-parameter tool, though it omits any note on result volume or ordering within groups.

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 nonetheless earns a bump by tying `top` to the ranking model (impact levels are relative to the scanned actors) and clarifying that `actor` returns score, sub-scores, praises and suggestions rather than a bare score.

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 resource (Apify quality score + improvement suggestions) with the exact grouping (work type) and ranking (impact) model. It also distinguishes its two operating modes, portfolio-wide top issues vs. a single actor's profile, so an agent can distinguish it from reporting siblings like actor_report or actor_profitability.

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 defines the two modes: omit `actor` for top issues across your top actors, supply `actor` for one actor's detail. What is missing is any guidance on when to pick this over sibling analysis tools (e.g., actor_report, run_health) or any prerequisite/auth notes.

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