Skip to content
AppGazers

Apps · MCP TOOL

list_rising_apps

List apps gaining traction from a small base.

Set up your assistant · Authentication and errors

When to use it

Discover newcomers using the collector’s rising score. period is accepted for compatibility but never selects the score window; use search_apps with sortBy=growth and growthPeriod for a chosen window. For country-specific chart filtering, use search_apps with ranked=true and country.

Parameters

NameTypeRequiredDefaultAllowed valuesDescription
sourcestringNo—apple_mobile, google_mobile, ios, androidStore: apple_mobile/ios or google_mobile/android.
categoriesstring[]No——Store category IDs or names. Maximum items: 20. Item minimum length: 1. Item maximum length: 80.
countrystringNo——only meaningful together with ranked=true Minimum length: 2. Maximum length: 2. Pattern: ^[a-z]{2}$.
periodstringNo"30d"7d, 14d, 30d, 60d, 90daccepted for compatibility only: it does not select the score window. The trending/rising score is one value per app that the collector computes over its own observed-history window; the result's `periodNote` repeats this. For a chosen window use search_apps with sortBy=growth and growthPeriod.
minReviewsintegerNo——Minimum rating/review count. Minimum: 0.
hasEstimatesbooleanNo——Filter by whether modeled estimates exist.
limitintegerNo20—Maximum number of results requested. Minimum: 1. Maximum: 50.
cursorintegerNo0—Zero-based offset; use the returned nextCursor to continue. Minimum: 0.
afterstringNo——Opaque keyset token from nextAfter; replaces the offset when provided. Minimum length: 1. Maximum length: 1024.

Defaults and constraints come from the published Zod input schema. “—” means no schema default or no enum restriction. Use JSON values of the listed type; additional handler rules are described above.

Example prompts

  • Show rising Google Play apps from a small base.

Example call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_rising_apps",
    "arguments": {
      "source": "google_mobile",
      "limit": 5
    }
  }
}

Example result

Illustrative, abridged JSON-RPC result. Only selected fields are shown; empty arrays illustrate a response with no rows. These are not current catalog observations. Parse the JSON inside content[].text.

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"data\":[],\"periodNote\":\"period=30d was not applied: the rising order is metrics.risingScore, one score per app computed by the collector over its own observed-history window, and it does not select a 30d window. Use search_apps with sortBy=growth and growthPeriod for a chosen window.\"}"
      }
    ]
  }
}

Free vs paid results

Free keeps identities for rows 1–10 by absolute position, locks identities at 11+, and hides revenue estimates. Basic and Pro unlock these fields. Explicit ID lists keep their named identities.

Paid access does not fill coverage gaps or unknown values. Returned plan metadata and lock notes explain redaction where applicable. Read the full Free data policy.

Rate limits and usage credit

PlanCalls per tool / dayAll tools / week
Free550
Basic100700
Pro3002,500

Days reset at 00:00 UTC. The combined ISO week resets Monday at 00:00 UTC. Every served tool call counts, including cached reads. Failed or refused calls are released along with any charge. Compare plans.

After either allowance, Basic and Pro can opt in to pay $0.02 in usage credit per call to list_rising_apps. A call exceeding both windows is charged once. Free is refused past its allowances; paid plans without opt-in or enough credit are also refused with HTTP 402 / JSON-RPC -32004.

Credential request throttles and, for live keyword work, store-work throttles also apply. Follow retry instructions in the error reference.