tools / track_config

track_config

not read-only

Manage tracked keywords

Tell the service once what to watch; it snapshots every day after that.

track_config manages your account's tracked set: the keyword × app × storefront combinations the hosted service snapshots automatically every day, server-side. Configure once; the daily managed run does the polling so neither you nor your agent ever re-checks ranks by hand.

add inserts the cross product of apps × keywords × countries (up to 500 combinations per account on the free tier), remove deletes by any filter combination, list shows the current set. The daily snapshots accumulate into per-series history that history reads back — current, best, worst, and movement.

This is the hosted replacement for the CLI's local config file: same model, but the schedule, storage and retries are the service's problem.

worked example

Start tracking HabitKit for two keywords in the US.

tools/call → track_config

{
  "name": "track_config",
  "arguments": {
    "action": "add",
    "apps": [
      6443918070
    ],
    "keywords": [
      "habit tracker",
      "streak tracker"
    ],
    "countries": [
      "US"
    ]
  }
}

track_config → structuredContent

{
  "tracked": [
    { "appId": 6443918070, "keyword": "habit tracker",  "country": "US" },
    { "appId": 324684580,  "keyword": "music",          "country": "US" },
    { "appId": 6443918070, "keyword": "streak tracker", "country": "US" }
  ],
  "total": 3,
  "added": 2
}

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

The response is always the full post-change set — here two combinations joined one already tracked, and added: 2 confirms the delta.
Adds are a cross product: 2 apps × 10 keywords × 3 countries registers 60 combinations in one call.
From the next daily run onward each combination gains a snapshot per day; track forces an immediate one when you can't wait.

when to use it

Right after shipping metadata: register the target phrases from your audit/coverage work and let the mornings accumulate evidence.
Watching a competitor's keywords — combinations track any appId, not just your own apps.
Pruning: remove by app, keyword or country filter keeps the set inside the 500-combination budget as targets change.
If you only ever want one-off checks with no server-side state, plain rank is enough — this tool exists for the daily cadence.

description — as served to agents

Manage this account's tracked set (the hosted replacement for the local track config file): every (app x keyword x storefront) combination is snapshotted by the daily managed run and on demand via the track tool. action=add inserts the cross product of apps x keywords x countries (cap 500 combinations per account); action=remove deletes combinations matching the given appId/keyword/country filters (at least one filter required); action=list just returns the current set.

input

action *

"list" | "add" | "remove"

apps

integer[]

trackIds to add (action=add)

keywords

string[]

keywords to add (action=add)

countries

string[]

2-letter storefront codes, e.g. ["US", "GB", "JP"]. Each storefront is queried separately; at most 25 per call.(default ["US"])

appId

integer

remove filter: only this app

keyword

string

remove filter: only this exact keyword

country

string

remove filter: only this storefront

output

tracked *

object[]

appId *

integer

keyword *

string

country *

string

total *

integer

added

integer

rows inserted; only for action=add

removed

integer

rows deleted; only for action=remove

pairs with

trackforce an immediate snapshot of the whole set›historyread the accumulated daily series back›auditwhere the keywords worth tracking come from›

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