Google Search Console integration for Model Context Protocol (MCP)
AppTail – ASO & Keyword Research is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
App Store keyword rankings, competitors, markets, reviews and analytics for iOS apps, from your AI.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http apptail-aso-keyword-research-mcp https://mcp.apptail.io/mcp
# 2 — ask your agent for something these tools do
# get_account, explain_period, get_performance and 22 more
AppTail – ASO & Keyword Research costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http apptail-aso-keyword-research-mcp https://mcp.apptail.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
25 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The account: its apps with Apptail ids, its plan and the limits that can refuse a write, App Store Connect health per app, how fresh the first-party data is, and the storefronts it focuses on. Call this first whenever the request is about "my app" or "my keywords" — every other tool needs an app_id, and the focus countries and hidden apps here are what keep your answer agreeing with what the custo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_hidden | boolean | no | Also return apps the owner has set aside. Default true, because they are still tracked and still answerable — each one is marked hidden: true, and they must be left out of portfolio totals. Set fals |
| include_competitors | boolean | no | Also return the rival apps tracked under this account's apps, each marked is_competitor. Default false: including them makes any portfolio total wrong, and get_competitors is the tool that answers q |
Return an account or owned-app summary for a requested period: available measured App Store Connect performance, storefront changes, tracked keyword movements, recorded signals, review volume and the last sent digest. Returns comparison data, coverage and caveats identifying unavailable sections. Reads account data without changing tracking or publishing content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | no | Narrow to one of the account's own apps — get_account lists them. Omit for the whole portfolio, which excludes apps the owner has hidden. |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
| compare | string | no | What to read the period against. previous (the default) is the period immediately before — for a calendar month, the calendar month before. year_ago is the same dates a year earlier, for compariso |
| country | string | no | Storefront for the keyword half only; the money is reported across all of them with a per-storefront split. Defaults to the app's primary storefront. Ranks only exist per storefront. |
Read measured App Store Connect impressions, store views, downloads, sales and proceeds for apps connected to the authenticated account. Supports an owned app or portfolio, documented time windows, period comparisons and breakdowns by storefront or traffic source. Returns the actual reporting window, connection coverage and caveats. Does not provide private analytics for apps outside the account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | portfolio (the default) sums every app the account owns; app reports one, and then app_id is required. Hidden apps are in the portfolio sum only if the account has not hidden them — they are exc |
| app_id | integer | no | Apptail app id, required when scope is app. Must be one of the user's own apps — get_account lists them. Measured analytics require an authorised App Store Connect connection for the account. |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
| compare | string | no | What to read the window against. previous (the default) is the period immediately before — for a calendar month that is the calendar month before, not the same number of days. year_ago is the same |
| split | string | no | Break the totals down. country gives one row per storefront Apple named; source gives Apple's own attribution — App Store search, browse, app and web referrers. source reports the attribution as |
| grain | string | no | Bucket size for the series. Omit and it is chosen to fit the window — a day for a month, a week for a year. A grain too fine or too coarse for the window is ignored rather than refused. |
| include_apps | boolean | no | On portfolio scope, also return one row per app so a portfolio move can be attributed to the app that caused it. Default false. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | no | Narrow to one of the user's own apps — get_account lists them. Findings about the competitors tracked under it are included, because a rival taking your places is something that happened to you. Omit |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
| types | array | no | Only these kinds of finding. Omit for all of them. An unknown name is refused rather than ignored, so a filtered answer is never returned as though it were unfiltered. |
| min_severity | string | no | Floor on how loudly a finding speaks. Default neutral, which is everything. warning drops a rival shipping a point release, which is worth knowing and not worth acting on. It is NOT the same as "w |
| include_sent | boolean | no | Mark the findings that already went out in an alert digest the user has read. Default false. Set it whenever you are about to summarise a period for someone: without it you cannot tell news from somet |
| limit | integer | no | Max findings, newest first. Default 50, capped at 200. The answer always says how many the window actually holds. |
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. Cyril
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | App name in any language, a bundle id (com.example.app), or a full App Store URL. Searches Apptail first and falls back to the App Store, importing anything it finds — so this returns a usable app_id |
| country | string | no | Storefront to search (e.g. "us", "ru"). Omit and it is guessed from the script the query is written in — Cyrillic implies ru, and so on. Pass it explicitly when the user names a market, because the gu |
| limit | integer | no | Max results. Default 10, capped at 25. |
Everything AppTail holds about one app, at the depth you ask for. The base answer is the store listing in one storefront — the localised title and subtitle a shopper in country actually reads, the price and its currency, version, category, release dates, the publisher's ids. include adds sections: prices (what it costs in every storefront), ratings (every storefront's rating and vote c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id. get_account for the user's own apps, search_apps for any other app in the store. Not the numeric id in an App Store URL (that is apple_app_id). |
| country | string | no | Storefront to read the listing in (e.g. US, GB, DE). Defaults to the app's primary storefront. Title, subtitle, price, rating and screenshots all differ per storefront, so this changes the answer rath |
| include | array | no | Extra sections to read. Omit for the listing alone, which is the cheap answer. ratings, charts and popularity need a Starter or Pro plan and are refused by name without one — the rest are free. |
| history_days | integer | no | With include: ["ratings"], also return the rating and the vote count day by day, this many days back from today, and how each storefront moved over that window — ratings_gained and `rating_cha |
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, Search Visibility (a 0–100 score per storefront with the terms that moved it), and the terms two of y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | app (the default) reads one app's corpus and needs app_id. portfolio reads every app the account owns and reports each term under whichever of them ranks best for it — that is the scope `include |
| app_id | integer | no | Apptail app id for one of YOUR apps — get_account lists them. Required for scope: "app". Not the numeric id in an App Store URL (that is apple_app_id). |
| country | string | no | Storefront to read ranks in (e.g. US, GB). Defaults to the app's primary storefront. Ranks only exist per storefront — the same term ranks differently in each — so one call answers for one market. |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
| keyword_ids | array | no | Only these terms, by Apptail keyword id — from this tool's own output or discover_keywords. Ids the account does not track are still answered when the scope is one app, because "how is my app doing fo |
| compare_with | array | no | Apptail app ids to measure on these same terms — from get_competitors or search_apps. Rivals are measured on YOUR corpus, not theirs. At most 5 are used and the answer names which; send the ones that |
| contains | string | no | Only terms whose text carries this substring, matched case-insensitively and applied before the sort and the cap. This is how to ask about a term by name — "how is mpg doing" — without looking up it |
| sort | string | no | movement (the default) puts terms that left the results first, then real drops by size — the top of the list is what to ask about. rank is best position first, volume is most searched (Apple pop |
| include | array | no | Extra blocks. history adds a day-by-day series per term, capped at 25 terms — pair it with keyword_ids for specific terms. visibility adds Search Visibility — the 0–100 answer to "is our ASO |
| tag_id | integer | no | Only keywords carrying this tag. Tag ids come back on the keywords in this tool's own output. Omit for the whole corpus. |
| limit | integer | no | Max terms returned, after sorting. Default 100, capped at 300. The answer always says how many the corpus holds. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword_id | integer | no | Apptail keyword id — from get_keywords or discover_keywords, or off a rank.move signal. The storefront is fixed by the keyword itself; a term is tracked per country. Give this OR keyword + `countr |
| keyword | string | no | The search term itself, for words a user typed rather than an id — "sleep tracker", "заметки". Needs country. A term nobody has ever looked up is created and the storefront is read live, so this ans |
| country | string | no | Storefront for keyword, e.g. "us", "jp". Required with keyword and ignored with keyword_id, because a keyword already names its storefront. There is no worldwide search results page — every App |
| date | string | no | The day to read, YYYY-MM-DD. Omit for the most recent crawl, which is the only mode that ever crawls live — naming a day is a question about the past and is answered from what was recorded. A day no |
| limit | integer | no | How deep to read. Default 25, capped at 50. Below about 25 nobody is competing with you for the term. |
Terms an app could be tracking but is not, merged from every source and each labelled with where it came from: what tracked competitors rank for, what the store's similar apps rank for, what those competitors put in their own titles and subtitles, what the store's own mining surfaced, and — reading the listing cold — what the app's own title, subtitle and description suggest. The last is the only
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id to suggest for. get_account for the user's own apps. Suggestions are derived from this app's listing, its rivals and its neighbours, so they are only meaningful for the app they were as |
| country | string | no | Storefront to suggest for (e.g. US, DE). Defaults to the app's primary storefront — which is only one of them: an app localized into several languages is searched for in several storefronts, so call o |
| source | array | no | Which sources to read. Omit for all five that need no argument — competitors, similar, listing, store, ai. corpus is a text match against terms AppTail already holds and does nothing witho |
| contains | string | no | Only terms containing this text. With source: ["corpus"] this is a search of AppTail's keyword database. Note it searches terms AppTail holds, not the App Store: a phrase nobody has ever tracked ret |
| limit | integer | no | Max suggestions, most-searched first. Default 60, capped at 200. The answer always says how many there were. |
Start tracking search terms for one of your apps, in one storefront. Send terms, or keyword_ids for suggestions returned by discover_keywords — a suggestion MUST be added by id, because re-resolving its term can land on a different keyword row. Counts against the plan's per-app keyword limit; dry_run reports what would happen without writing anything. Terms already in the corpus come back unde
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — get it from get_account. Not the numeric id in an App Store URL (that is apple_app_id). Keywords are tracked per app. |
| keywords | array | no | Search terms to start tracking, as a user would type them into the App Store (e.g. ["fitness tracker", "workout app"]). Send the whole batch in one call rather than one term per call. Terms we have ne |
| keyword_ids | array | no | Apptail keyword ids to start tracking — the keyword_id on a discover_keywords row. Use this rather than the term whenever you have an id: a term is re-resolved and can land on a different keyword ro |
| country | string | yes | Storefront to track these terms in, ISO 3166-1 alpha-2 (e.g. US, GB, DE). Required and not defaulted: a term tracked in the wrong storefront is a wasted keyword slot. Ranks are per storefront — the sa |
| dry_run | boolean | no | Report what would be added, and how many slots are left, without tracking anything. Nothing is written and nothing counts against the plan. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — get it from get_account. Not the numeric id in an App Store URL (that is apple_app_id). |
| keyword_ids | array | yes | Apptail keyword ids to stop tracking, as returned by get_keywords. Ids, not terms — two apps can track the same word and only these rows are removed. Frees the slots against your plan limit. Position |
Put tracked keywords under a tag, in bulk — or clear their tag — and/or say whether they are brand terms for Search Visibility. The tag is named, not looked up: a name that does not exist yet is created. A keyword carries at most one tag, so assigning replaces whatever it had. brand is separate from tags: own (your app's name) and competitor (a rival's name) leave the terms out of the visibi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — from get_account. Tags belong to an app. |
| keyword_ids | array | yes | Apptail keyword ids to tag, as returned by get_keywords. Ids, not terms. Up to 500 in one call. A keyword the app does not track is reported back rather than silently ignored. |
| tag | string | no | The tag name to put them under. Created if it does not exist. Omit — or send null — to clear the tag off these keywords instead. |
| color | string | no | Hex colour for a tag being created, e.g. "#2563eb". Ignored when the tag already exists. Omit and one is picked from the palette that the app is not already using. |
| brand | string | no | Whether these terms are somebody's name, for Search Visibility (get_keywords include: ["visibility"]). own = your app's name, competitor = a rival's: both are listed and left out of the score, b |
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 comp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — get it from get_account. Not the numeric id in an App Store URL (that is apple_app_id). |
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_keyword
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — get it from get_account. Not the numeric id in an App Store URL (that is apple_app_id). |
| country | string | no | Storefront to read the niche in (e.g. US, GB). A niche exists per storefront and is never blended across them. Defaults to the first of the account's focus_countries this app is actually tracked in, t |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
Track one or more rival apps against one of YOUR apps. Each competitor can be given as an Apptail app_id, an App Store URL, or just a name — names and URLs are resolved and imported the way search_apps does, so you do NOT need to look up an app_id first. Returns one outcome per item: what was added, what was already tracked, and what a plan limit refused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — from get_account. The rivals are tracked FOR this app: competitor sets belong to an app, not to the account, so removing one later affects only this app. |
| competitors | array | yes | The rivals, up to 20. Each item is an Apptail app_id, a full App Store URL, or an app name in any language. Send all of them in one call — the plan limit is checked per item, so a batch that runs out |
| country | string | no | Storefront to resolve names in, ISO 3166-1 alpha-2 (e.g. US, DE). Omit and it is guessed from the script the name is written in. Ignored for items given as an app_id. |
| dry_run | boolean | no | Resolve every item and report what would happen, without tracking anything. Use it when the user named apps ambiguously and you want to confirm you found the right ones before changing their account. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id for one of YOUR apps — from get_account. Only this app's competitor set is touched. |
| competitors | array | yes | The rivals to stop tracking, up to 20. Each item is an Apptail app_id (as returned by get_competitors), a store URL, or a name. Ids are the reliable form here — a name is resolved against the whole st |
Add an app to the account as one of the user's own. Takes an Apptail app_id, an App Store URL, or a name — resolved and imported the way search_apps does. Tracking starts immediately (rankings, reviews, competitors); measured downloads and proceeds still require connecting App Store Connect in the console, which cannot be done from here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | yes | The app to claim: an Apptail app_id, a full App Store URL, or the app's name. A URL is the reliable form — a name resolves against the whole store, and two apps can share one. |
| country | string | no | Primary storefront for this app, ISO 3166-1 alpha-2 (e.g. US, DE). Defaults to US. This is the storefront its keywords and rankings are tracked in first; more can be added in the console. |
| dry_run | boolean | no | Resolve the app and report what would happen without claiming it. Worth doing when the user gave a name rather than a URL, so they can confirm it is the right app before it counts against their plan. |
Read iOS App Store niche data by saved market_id or by query and countries. Returns storefront competition, search visibility, app membership and optional corpus or movement data. Phrase research can create shared keyword records and persist crawled search observations; it does not save an account market. Downloads and revenue are labelled third-party rolling 30-day estimates. Reports per-storefro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market_id | integer | no | Apptail market id for a market this account has saved — from list_markets. A saved market is a pure read: no crawling, sub-second. Send this OR query, not both. |
| query | string | no | A phrase to resolve into a market right now, e.g. "AI calorie tracking". Requires countries. Can persist shared keywords and search observations. No market is saved to your account — call save_marke |
| countries | array | no | Storefronts to ask the question in, ISO 3166-1 alpha-2 (e.g. ["US","GB","DE"]). Required with query. Each storefront gets its own corpus seeded from the same phrase; that is deliberate, and a phrase |
| store | string | no | Read only this one storefront of a saved market. Omit for every storefront compared, which is where overlap and the contest range come from. |
| include | array | no | Extra sections, each costing a query: members (the leaderboard), corpus (every term with why it is in), movement (who arrived and who left), app_terms (which terms ONE app holds here and wheth |
| app_id | integer | no | Scopes include: ["app_terms"] to one app — an Apptail app id from members, search_apps or get_landscape. This is the audit trail for membership: it returns every (term, storefront) place that |
| new_within_days | integer | no | Keep only apps FIRST RELEASED inside this many days — "what has launched into this niche lately". Applied to every app ranking for the corpus before the list is cut, so these are the new apps in the m |
| budget_seconds | integer | no | How long a live query may spend crawling, shared across ALL storefronts rather than each. Default 5, max 30. It is rarely the binding limit — at most 12 terms are crawled per call whatever the clock |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
List markets saved by the authenticated account, including market ids, storefronts, competition ranges, app counts and observed changes for the requested period. Reads saved account configuration and market observations without creating, updating or deleting markets. Returned ids can be used with get_market.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
Create or update a saved market in the authenticated account from a query, countries and optional per-storefront seed terms. An existing name updates that market, adding storefronts or replacing seed configuration and rebuilding requested storefronts. Persists account configuration and queues background corpus collection using public App Store data. Requires write authorisation. Returns market_id,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The phrase to build the market from, e.g. "AI calorie tracking". Used as the seed in every storefront unless seeds overrides it. |
| countries | array | yes | Storefronts to ask it in, ISO 3166-1 alpha-2 (e.g. ["US","DE"]). Each keeps its own corpus; nothing is blended across them. |
| name | string | no | What to call it. Defaults to query. Passing the name of a market this account already has ADDS the new storefronts to it rather than creating a second one. |
| seeds | object | no | Per-storefront seed terms, keyed by country code: {"de": ["kalorienzähler"]}. OPTIONAL, and optional per storefront. A storefront you leave out is not seeded from query: its terms are read off the l |
Add terms to one storefront's corpus, or take terms out of it. Add for a term the corpus SHOULD hold and does not — a rival's brand, a phrase Apple has never measured the popularity of, the term a thin storefront is really about; a pinned term is kept through every rebuild and refreshed on the same 72-hour cadence as the rest. Remove for a term that does not belong: ANY term can go, and one the he
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market_id | integer | yes | Apptail market id — from list_markets or save_market. |
| country | string | yes | Which storefront's corpus, ISO 3166-1 alpha-2 (e.g. US, DE). Required and not defaulted: a corpus belongs to one storefront, and there is no market-wide term list to add to. |
| add | array | no | Terms to pin, as somebody would type them into the App Store. Send the batch in one call. Terms already in the corpus come back under already_present rather than as an error. |
| remove | array | no | Keyword ids to take out of the corpus — the keyword_id on ANY get_market corpus row. A term the heuristic found is also recorded as excluded so rebuilds do not re-derive it; add on the same term l |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market_id | integer | yes | Apptail market id — from list_markets. |
| store | string | no | Drop only this storefront, ISO 3166-1 alpha-2. Omit to delete the whole market. Dropping the last storefront deletes the market too, because a market asked nowhere is not a market. |
Get top app charts (free, paid, or grossing) for a store, country, and category.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | no | Only the App Store is covered. Google Play is in the data model but nothing is crawled for it, so omit this. |
| country | string | no | Storefront to read the chart for (e.g. US, GB, JP). Defaults to US. An unrecognised code falls back to US rather than failing — the reply echoes the storefront actually used, so check it. |
| category | string | no | Apple category id as a number, e.g. 6014 Games, 6015 Finance, 6017 Education, 6023 Food & Drink, 6013 Health & Fitness, 6012 Lifestyle. Omit for the overall chart across all categories. An id we do no |
| chart_type | string | no | Which chart. Default free. Use grossing for revenue questions — top free ranks by downloads and says nothing about money. An unrecognised value falls back to free and the reply says which chart it rea |
| limit | integer | no | How deep to read the chart. Default 25, capped at 100. |
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 "
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | integer | yes | Apptail app id. get_account for the user's own apps, search_apps for any other. Reviews are readable for any app in the store, including competitors. |
| period | string | no | The window to report on. A calendar month as 2026-07, a calendar year as 2026, last_month, this_month, last_year, or a trailing window: today, 7d, 14d, 30d, 90d, 180d, 365d, `7 |
| from | string | no | Start date, YYYY-MM-DD, inclusive. Overrides period when both are sent. Send it alone and the window runs to today. |
| to | string | no | End date, YYYY-MM-DD, inclusive. Send it alone and the window is the three years before it. |
| country | string | no | Only reviews from this storefront (e.g. de). Omit for every storefront, which is usually right — one storefront's reviews are a thin sample. Send it when ratings.by_country on get_app has pointed at |
| rating | array | no | Only these star ratings, e.g. [1, 2] for the critical ones. Omit for all five. The summary counts are deliberately NOT filtered by this, so a call asking only for one-stars still learns how many r |
| contains | string | no | Only reviews whose title or body contains this text, case-insensitively. Title as well as body, because a complaint is as often the headline as the paragraph. This is how you check a hypothesis — "cra |
| unanswered | boolean | no | Only reviews the developer has never replied to. False or omitted for all of them. Combined with rating: [1, 2] this is the work queue the console leads with — and a backlog has no window, so se |
| limit | integer | no | Max reviews, newest first. Default 25, capped at 200. The answer always says how many matched. |
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 ite
| Parameter | Type | Required | Notes |
|---|---|---|---|
| replies | array | yes | The replies, up to 10 per call. Send them in one call rather than one at a time: each is answered separately, so a batch where one app is not covered still posts the rest and says which it did not. |
| dry_run | boolean | no | Check every item and report what would happen, without publishing anything. Worth using by default here — it confirms the reviews resolve, the account's key reaches their apps and the text fits, b |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AppTail – ASO & Keyword Research or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish AppTail – ASO & Keyword Research can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.