Alerts · MCP TOOL

get_alerts

Read daily app events or the global event ticker.

Set up your assistant · Authentication and errors

When to use it

With appIds, read events for named apps; since applies only to that mode. Without appIds, days selects a global ticker with at most one event per app. The ticker promotes low severity to medium and caps limit at 100.

Parameters

Name	Type	Required	Default	Allowed values	Description
`appIds`	string[]	No	`—`	—	watchlist ids; omit for the global ticker Minimum items: 1. Maximum items: 200. Item minimum length: 1. Item maximum length: 210.
`types`	string[]	No	`—`	rank_move, review_spike, new_ads, ads_stopped, estimate_change	Event types to include.
`minSeverity`	string	No	`"low"`	low, medium, high	Lowest event severity to include.
`since`	string (date-time)	No	`—`	—	only with appIds; the ticker uses `days` instead
`days`	integer	No	`3`	—	how far back the global ticker looks Minimum: 1. Maximum: 30.
`limit`	integer	No	`20`	—	Maximum number of results requested. Minimum: 1. Maximum: 200.
`cursor`	integer	No	`0`	—	Zero-based offset; use the returned nextCursor to continue. Minimum: 0.

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 recent chart moves for Facebook.

Example call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_alerts",
    "arguments": {
      "appIds": [
        "ios:284882215"
      ],
      "types": [
        "rank_move"
      ],
      "minSeverity": "medium"
    }
  }
}

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\":[]}"
      }
    ]
  }
}

Free vs paid results

Explicit appIds keep their identities on Free; the global ticker locks identities after position 10. Revenue figures in estimate-change events are hidden. Paid plans unlock these fields.

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

Plan	Calls per tool / day	All tools / week
Free	5	50
Basic	100	700
Pro	300	2,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 get_alerts. 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.