Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Store rank by keyword

store_rank
Read-onlyIdempotent

Look up your Apify Store rankings for up to 10 keywords: see where your actors appear in search results and which competitors rank above them.

Instructions

Your actors' positions in Apify Store search for up to 10 keywords, in the order a Store visitor sees, with the actors ranked above your best one.

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": {
      "keywords": "<keywords>"
    },
    "name": "store_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoHow many Store results to scan per keyword (1–100, default 50).
keywordsYes1–10 keywords to look up in the Apify Store.

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful result semantics — positions are ordered as a Store visitor sees them, and surrounding higher-ranked actors are included — but says nothing about latency or cost of scanning depth times keywords, which matters for a live open-world lookup.

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 front-loaded sentence with no filler, covering scope and result ordering. The trailing clause 'with the actors ranked above your best one' is slightly awkward but conveys real information about what comes back.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two fully documented parameters, annotations present and no output schema, the definition is close to sufficient. It still leaves unclear what a 'position' value looks like and how expensive a 10-keyword by 100-depth scan is, which an agent scheduling calls would want to know.

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?

Schema description coverage is 100%, so both keywords and depth are already documented including their bounds and defaults. The description only restates the 10-keyword cap and adds no meaning for depth, so the baseline 3 applies.

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 resource (your actors' positions in Apify Store search) and the scope (up to 10 keywords), which is enough to tell it apart from scoring/report siblings like acquisition_score or revenue_summary. It stops short of a crisp verb such as 'fetch' or 'check', and it does not explicitly contrast with competitor_benchmark, the nearest neighbor.

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 named alternative. An agent must infer from the name and the sibling list that this is the tool for keyword-level Store visibility tracking rather than profitability or quality scoring.

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