tools / track

track

not read-only

Track configured keywords

Snapshot every tracked rank right now and report the movement.

track runs your account's whole tracked set immediately: one throttled search per keyword × storefront, every configured app's rank recorded server-side, and a movement report per combination against its previous snapshot.

You rarely *need* it — the managed run already snapshots every combination daily — but “we just shipped, where are we now?” deserves an answer that doesn't wait for tomorrow's run. Efficiency is preserved: each keyword × storefront is searched once for all configured apps, not once per app.

Results append to the same server-side history the daily run writes, so an on-demand snapshot becomes part of the permanent series history reads.

worked example

Snapshot the tracked set right after adding HabitKit combinations.

tools/call → track

{
  "name": "track",
  "arguments": {}
}

track → structuredContent

{
  "apps": [6443918070, 324684580],
  "keywords": ["habit tracker", "music", "streak tracker"],
  "countries": ["US"],
  "tracked": 3,
  "results": [
    { "appId": 6443918070, "keyword": "habit tracker", "country": "US",
      "appName": "Habit Tracker - HabitKit", "rank": 2,  "totalResults": 189,
      "change": "no previous record" },
    { "appId": 324684580, "keyword": "music", "country": "US",
      "appName": "Spotify: Music and Podcasts", "rank": 3, "totalResults": 179,
      "change": "unchanged at #3" },
    { "appId": 6443918070, "keyword": "streak tracker", "country": "US",
      "appName": "Habit Tracker - HabitKit", "rank": 10, "totalResults": 193,
      "change": "no previous record" }
  ]
}

real response, captured 2026-07-29 — trimmed only where marked with …

change is already computed against each combination's previous snapshot — "no previous record" marks a series being born, "unchanged at #3" an existing one holding.
The run costs one search per keyword × storefront (throttled ~1/s) regardless of how many apps share the keyword; progress notifications stream for clients that request them.
Takes no arguments at all: the tracked set *is* the specification, managed via track_config.

when to use it

The hour after a metadata release, when tomorrow's scheduled snapshot is too far away.
Establishing a baseline the moment new combinations are added, so day-one movement is measurable.
Ad-hoc portfolio sweeps during an incident (“did the update tank our ranks?”) with the movement report inline.
For a single keyword question, use rank — track always runs the whole set and spends quota accordingly.

description — as served to agents

Snapshot ranks for every (app x keyword x storefront) in this account's tracked set (manage it with track_config) and report movement per combination. Snapshots are stored server-side per account; a managed run also happens daily, so calling this is only needed for an immediate refresh. One throttled search per keyword x storefront (~1s each); progress notifications are sent when requested.

input

no parameters

output

apps *

integer[]

keywords *

string[]

countries *

string[]

tracked *

integer

combinations in the tracked set

results *

object[]

appId *

integer

keyword *

string

country *

string

appName *

string | null

rank *

integer | null

totalResults *

integer

change *

string | null

pairs with

track_configdefine the set this tool snapshots›historythe series these snapshots accumulate into›rankthe one-off version of the same question›

endpoint https://mcp.openaso.ai/mcp · auth Authorization: Bearer <key> · get a key