Skip to main content
Glama
storelift-mcp

storelift-mcp

Keyword ranks

get_keywords
Read-onlyIdempotent

Retrieve keyword ranks for a specific app in a chosen App Store or Google Play country to track visibility and distinguish unmeasured queries from absent rankings.

Instructions

Keyword ranks for one app in one App Store / Google Play country. THREE STATES ARE DISTINCT: measured=false means the query could not be measured, rank=null means it was measured but the app is absent from the top results, rank= is the rank. Never collapse them into one — counting an unmeasured day as zero produces a false answer.

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": {
      "appId": "<appId>"
    },
    "name": "get_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesapp id from list_apps
countryNocountry code, e.g. tr, us (defaults to the app's first country)
platformNodefaults to ios

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the result set contains three semantically distinct states (measured=false, rank=null, rank=number) and misinterpreting them yields false answers. This is exactly the kind of interpretation hazard annotations cannot express. Minor gap: it does not say what causes measured=false or what the overall response shape is.

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 core scope in one sentence, then the critical caveat. The three-state sentence is emphatic but justified because collapsing the states is the primary failure mode. Slightly verbose in the reprimand clause, though it earns most of its 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?

With no output schema, the description carries the burden of explaining return-value semantics, and it does so precisely on the one dimension that matters (the null/false/number distinction). It is a little thin on when measured=false occurs and what the payload actually contains per keyword, but an agent can call it without further information.

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%, with appId source, country default and platform default all documented in-schema, so the baseline is 3. The description reinforces the cardinality ('one app in one country') but adds no format or enumeration detail beyond what the schema already provides.

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?

States a specific resource and scope: keyword ranks for a single app in a single App Store/Google Play country. The object and cardinality constraints are clear enough to call it correctly, but it never distinguishes itself from the sibling hive_keyword_ranks, so an agent cannot tell the two apart from the text alone.

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?

The 'one app in one country' scoping implies when this is the right call, and the three-state warning implies when the data is trustworthy. However, there is no explicit when-not guidance and no named alternative among the many keyword siblings (hive_keyword_ranks, get_keyword_metrics, hive_keyword_spy), which is a real gap for an agent choosing between them.

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