Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Compare with another creator

competitor_benchmark
Read-onlyIdempotent

Compare your public Apify creator portfolio against another creator's to benchmark actor counts, 30-day users, total runs, and top five actors.

Instructions

Your public portfolio vs another creator's: actors, users (30 days), median users per actor, actors with 10+ and 100+ users, total runs, and each side's top 5 actors.

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": {
      "username": "<username>"
    },
    "name": "competitor_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesAnother Apify creator's username to compare against the connected account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this a safe, read-only, idempotent, non-destructive external read. Beyond that the description adds the 30-day measurement window and the fact that only the public portfolio is compared, which is useful scope context, but it does not disclose authorization requirements, result ordering, or any caveats about what counts as a 'user'.

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?

A single sentence that front-loads the comparison and then enumerates the returned metrics with no filler. The dense metric list is justified because no output schema exists, though it reads as an inventory rather than a structured narrative.

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 one required parameter and no output schema, listing the metrics returned is the right compensation and largely covers the return shape. Gaps remain around what the response looks like structurally and any limitations of public-only data, but nothing critical to invoking it is missing.

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 parameter with full schema description coverage, so the baseline is 3. The description reinforces that the username refers to 'another creator' and that the baseline side is the connected account's public portfolio, which is modest added meaning rather than new semantics.

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 the specific comparison ('Your public portfolio vs another creator's') and enumerates the exact metrics produced (actors, users over 30 days, median users per actor, 10+/100+ user actors, total runs, top 5 actors). It is clearly a comparison/benchmarking tool, distinguishable from reporting siblings like actor_report, though it never uses an explicit verb such as 'compare'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named for cases where the agent wants per-actor detail rather than a portfolio-level scorecard. The comparison framing implies the use case but leaves selection against siblings such as actor_report or growth entirely to inference.

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