AppTail

DEPRECATED — use get_reviews, which takes a date window and filters by star rating, text and whether the developer replied, and returns the volume and rating trend beside the list. Get recent reviews for an app, optionally filtered by country.

get_app_reviews

List tracked competitor apps for one of your apps, with how many more the plan allows — and `suggested`: up to ten rivals the account does not track yet, ranked by how many of the app's own search terms they sit in the top ten for. Works on an app with no keywords: its listing is read for terms and the store is crawled for them. Read `suggested_basis.terms_pending` before calling a short list complete. Suggestions can persist shared keyword records and queue background crawls. Suggested apps are not added to your competitor watchlist.

get_competitors

DEPRECATED — use get_app with `include: ["developer"]` on any of the publisher's apps. Get developer/publisher profile including app portfolio and contact info.

get_developer_info

The App Store search results for one term in one storefront, on one day: who ranked, in what order, with their names, subtitles and ratings. This is how you find out WHO took the places an app lost — a rank that fell is a fact, and the results page on the day it fell is the reason. Works for ANY term in the store, tracked or not, known to us or not: pass `keyword_id` for a term you already have an id for, or `keyword` + `country` for words a user typed, which resolves the term and crawls the storefront live when what we hold is over a day old. Omit the date for the most recent crawl. A lookup can persist a new shared keyword record and queue a background crawl that updates stored search observations. It does not track the keyword for your account.

get_keyword_serp

DEPRECATED — use discover_keywords, which reads five sources rather than two, labels each suggestion with where it came from, and reaches the AI pass this tool cannot. Get keyword suggestions for an app based on competitors and similar apps.

get_keyword_suggestions

The account's tracked keywords for an app — or across the whole portfolio — over any window: where each term ranked at the start and end, how far it moved, how many days it held and how many days it was measured, and optionally its day-by-day history, the same terms measured for named competitors, the daily top-1/3/10/30/50/100 counts, and the terms two of your own apps are both on. Sorted worst movement first by default, so "what dropped" is at the top of a 300-term corpus — which also makes the returned rows a selection rather than a sample: `movers` and `coverage` are counted over the whole corpus and are what a summary comes from. Filter by `contains` to ask about one term by name. This is the tool for every question about tracked terms; it replaces get_tracked_keywords, get_keyword_positions and compare_keyword_positions.

get_keywords

Who the App Store shows beside one of your apps for the terms it competes on, in one storefront: every app in the niche with how many of your terms it ranks for and owns the top 10 for, its ratings, its review flow and its size, plus which apps arrived or fell out this window — and `term_gap`, how much of the niche's own vocabulary you do not track yet, with the biggest holes ready for add_keywords. This is the niche, not your watchlist: most rows are apps nobody added, and get_competitors answers the other question.

get_landscape

How contested a niche is, in one or more storefronts at once — the apps ranking for its terms, how much of the search results the top three own, who arrived this window, and how much of the leaderboard is the same everywhere. Pass `market_id` for a saved market (a pure read, no crawling) or `query` plus `countries` for any phrase, which can create shared keyword records and persist crawled search observations, but does not save a market to your account. Contest is measured from our own daily ranks; downloads and revenue are a third-party model and are marked as estimates. Nothing is ever averaged across storefronts: contest comes back as a range and the apps as a union.

get_market

Measured impressions, store views, downloads, sales and proceeds from App Store Connect, for one of the user's own apps or for their whole portfolio, over any window. This is the only tool that returns money or install counts, and it returns them only for apps the account has connected — Apple does not sell anyone else's. Optionally split by storefront or traffic source, and compared against the previous period or the same period last year.

get_performance

Reviews for any app over a window, filtered by storefront, star rating, text, or whether the developer has replied — plus the shape of the period: how many arrived per bucket, what they averaged, and where the app's pooled store rating stood while they did. Reviews exist for every app whether or not App Store Connect is connected, because they are read from the public store. This is the tool for "what are people complaining about": filter it and read the reviews yourself rather than asking for a summary. Every review says whether it can be answered (`can_reply`) and where an existing reply stands (`reply_state`); `reply_to_reviews` is what answers them. Replaces get_app_reviews.

get_reviews

What actually happened, from the record the product keeps: rank moves on tracked terms, chart entries, review spikes, competitor releases and price changes, plus — for the user's own apps only — week-over-week traffic and conversion shifts, download collapses, new reviews and rating moves. Each carries the two numbers behind it and the sentence that states the finding. This is a stored table read, not a reconstruction, so it is both cheaper and more reliable than diffing rank histories yourself. Covers the user's own apps and the competitors tracked under them; a rival's finding never `asks_action`.

get_signals

Get top app charts (free, paid, or grossing) for a store, country, and category.

get_top_charts

Every market this account has saved, with how contested each one is, how many apps are in it, how many arrived this window and which storefronts it is asked in. Use it to find a market_id for get_market, or to answer "how are my niches doing" in one call. Contest comes back as a range across storefronts and is never averaged.

list_markets

Remove one or more competitor tracking relationships for an app owned by the authenticated account. Accepts AppTail app ids, App Store URLs or names. Name and URL resolution can query the public App Store and import shared app records. Removes the selected pairing only; public apps and pairings for other apps remain. Requires write authorisation and returns one outcome per item.

remove_competitors

Remove tracked keywords from an app. Frees the slots against the plan limit; position history is kept, so re-adding a term later does not start from nothing.

remove_keywords

Delete a saved market, or just one of its storefronts. Pass `store` to drop a single storefront and leave the rest of the market with its corpora and its build clocks untouched; omit it to delete the whole market. Deleting frees a slot on the account's plan. The terms themselves are not deleted — they are shared with any other market or tracked app using them.

remove_market

Create, update or remove public App Store review responses for apps owned by the authenticated account, using its connected App Store Connect API key. Requires write authorisation and eligible review ids. Submitted text is sent verbatim under the developer's name. Obtain approval for the exact text or requested removal before submitting. dry_run validates without publication. Accepts up to ten items and returns per-item outcomes; pending means Apple has accepted a response but has not published it.

reply_to_reviews

Keep a market so it is monitored and reads back instantly. Give the phrase and the storefronts to ask it in; each storefront gets its own corpus, expanded from the seeds and then refreshed every 72 hours. Only ONE storefront needs a phrase in its own language — the rest read theirs off the localised listings of that one's leaders and confirm each phrase against the store before keeping it, so a market asked in nine countries no longer needs nine translations. Call it with the same `name` to add storefronts to a market that already exists. The build runs in the background — get_market on the returned market_id shows each storefront as it lands.

save_market

Search for iOS apps by name, bundle ID, or App Store URL. Supports all languages including Cyrillic, Chinese, etc. If the app is not in our database, it will be fetched from the App Store, persisted as a shared public app record, and queued for enrichment. This does not add the app to your account or competitor watchlist. Auto-detects the likely App Store region from the query language (e.g. Cyrillic → Russia, Chinese → China). To add what you find, add_competitors and add_app take the same name or URL directly — you do not have to look up an app_id first.

search_apps

DEPRECATED — use discover_keywords with `source: ["corpus"]` and `contains`, which searches the same database and returns the four suggestion sources beside it. Search for keywords in the database by term.

search_keywords

Put tracked keywords under a tag, in bulk — or clear their tag. The tag is named, not looked up: a name that does not exist yet is created. This is the tool for organising a large corpus after reading it with get_keywords ("tag every branded term as brand"), which is drudgery in the console and one call here. A keyword carries at most one tag, so assigning replaces whatever it had.

tag_keywords