Skip to main content
Glama
storelift-mcp

storelift-mcp

Store page signals

get_store_page
Read-onlyIdempotent

Read an app's App Store or Google Play page for one country to capture version, screenshots, install count, ratings and ranking changes for rank diagnostics.

Instructions

The app's own store listing signals for one country (name and subtitle are not included): version, in-app events, editorial placements, similar-apps shelves and the screenshot set (iOS), plus the Google Play page (exact install count, rating histogram, ad/IAP flags, chart badge). ios.listingExtras holds the languages the app supports, its star breakdown (1★ to 5★), live and upcoming in-app events, the promotional text and the featured in-app purchases; when the workspace's plan shows part of it, it carries the language count, the first 5 languages and the star breakdown, and locked shows how many of the rest there are. timeline lists the dated changes we detected on the listing — the cheapest explanation for a rank move. measured=false means the page was never read; it is not the same as an empty page.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / country / description
      Previous value: -"country code, e.g. tr, us"New value: +"country code, e.g. tr, us (defaults to the app's first country)"
  2. First observedv1.1.1

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it discloses deliberate exclusions (name and subtitle are not included), plan-based partial gating with `locked` counts, and the meaning of `measured=false` versus an empty page. That last point is exactly the kind of state semantics an agent cannot get from annotations.

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?

The most important claim is front-loaded in the first clause, and every sentence carries field-level or state-level information rather than filler. It is, however, one very dense run-on paragraph mixing response fields, plan gating, and the measured flag, which makes it harder to scan than a short structured breakdown would be.

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

Completeness5/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 must carry the return contract, and it does: it splits iOS versus Google Play content, names the `ios.listingExtras` and `timeline` blocks, explains the chart/rating/install fields, and clarifies the plan-limited and never-measured cases. For a two-parameter read tool this leaves no material gap for correct invocation or interpretation.

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 coverage is 100% for both parameters, including the country default and the fact that appId comes from list_apps, so the baseline is 3. The description reinforces the per-country scoping ('for one country') but adds no format, validation, or edge-case detail about the parameters themselves.

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 opening clause names a specific resource and scope: the app's OWN store listing signals for one country, and it enumerates the concrete payload (version, in-app events, editorial placements, similar-apps shelves, screenshots, plus the Google Play page). It implicitly separates itself from rival-oriented siblings like get_rival_detail by stressing 'the app's own', but it never names an alternative tool, so the boundary with get_listing_timeline and get_featuring (whose content it partly absorbs) has to be inferred.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. The only usage-like signal is 'timeline lists the dated changes we detected on the listing — the cheapest explanation for a rank move', which implies a diagnostic use case but leaves the agent to decide on its own.

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