Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Actor report

actor_report
Read-onlyIdempotent

Get a full report for one actor: users, 30-day runs, flags, price, memory, timeout, current build, reviews, source folder, and three-month revenue with break-even costs.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actor": "<actor>"
    },
    "name": "actor_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesThe actor: id, name, username/name, or title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the money section is conditional on a Console session being available, run results are scoped to 30 days, and financial history is limited to the last three months. It does not describe response shape or size, but with no output schema that is the main remaining gap.

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?

One sentence, front-loaded with the core promise, then a compact list of payload sections. Every clause corresponds to a distinct part of the return value, so nothing is filler despite the length.

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 read-only, single-parameter aggregate tool with no output schema, the description does the essential job of telling the agent what fields come back and which are conditional. Missing only edge-case behavior such as failure when the actor cannot be resolved or how large the payload may be.

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?

There is a single required parameter with 100% schema description coverage, and the schema already states it accepts an id, name, username/name, or title. The description adds no resolution-order or ambiguity guidance (e.g. which identifier form wins, what happens on a partial name match), so it sits at the baseline for a fully documented schema.

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?

Opens with a specific verb-and-resource framing ("Everything known about one actor") and then enumerates the concrete sections returned: users, run results, flags, price, memory/timeout, latest build, reviews, source folder, money. That enumeration makes it identifiable as the aggregate/superset report relative to narrower siblings like actor_profitability and actor_quality, though no sibling is named explicitly.

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?

Usage is only implied: the agent can infer this is the tool to call when it wants a full picture of a single actor. There is no explicit when-to-use vs when-to-prefer actor_profitability/actor_quality/run_health, and no exclusions or cost/size caveats. The parenthetical "(with a Console session)" is the only conditional guidance offered.

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