Skip to main content
Glama

AppTail – ASO & Keyword Research

Get Keyword Serp

get_keyword_serp

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe 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 nobody crawled comes back empty with `crawled: false` rather than as an error; pick one from `crawled_days`, which the answer always returns.
limitNoHow deep to read. Default 25, capped at 50. Below about 25 nobody is competing with you for the term.
countryNoStorefront 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 Store search happens in one country.
keywordNoThe 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 answers for any search in the store and not only for terms Apptail already holds. Prefer `keyword_id` when you have one: it is the exact row, where words go through the store's own normalisation first.
keyword_idNoApptail 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` + `country`, not both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
appsYesThe results in rank order, best first. `is_mine` marks the account's own apps and `is_tracked_competitor` marks rivals it already watches — a high-ranking app that is neither is worth suggesting they add.
dateNoThe day actually read, which is the day asked for or the most recent crawl. Null when nothing has been crawled for this term.
countYesApps returned.
countryNoStorefront these results come from. Fixed by the keyword.
crawledYesWhether that day had a crawl at all. False with an empty list means nobody measured, **not** that nobody ranked.
keywordYesThe search term itself.
refreshedYesTrue when this call read the App Store rather than the database — a term looked up for the first time, or one whose last crawl was over a day old. False means these are stored results; `date` says which day they are from. Do not describe results as live unless this is true.
keyword_idYesThe term that was read.
popularityNoApple search popularity for the term, roughly 5-100. Higher means more searched. Read it before calling a position valuable.
console_urlNoWhere this search is shown in the console, with the icons and screenshots this payload leaves out.
my_positionNoThe best rank held here by one of the account's own apps, or null when none of them are in these results. Null is not -1: it means no app of theirs appears in the depth that was read, which is not the same as being measured and absent.
crawled_daysYesDays in the last 30 that were crawled, newest first. Name one in `date` to see how the results looked then — comparing two days is what shows who took a place.
results_countNoHow many apps the store returns for this term in total. The results below are the top of that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses behavior well beyond annotations: a lookup can persist a new shared keyword record and queue a background crawl that updates stored observations, and can crawl the storefront live when cached data is over a day old. This reconciles the apparent read-only framing with readOnlyHint=false, and adds the empty-result semantics (`crawled: false`, not an error).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then input modes, then side effects. Some sentences are rhetorical rather than operational ('a rank that fell is a fact, and the results page on the day it fell is the reason'), but nearly every clause carries usable information for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return shape need not be explained. The description covers purpose, input mode selection, live-vs-recorded behavior, empty-day semantics, and the mutation side effect — complete for a 5-param open-world lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter constraints the schema does not: keyword_id vs keyword+country are mutually exclusive, and country is ignored with keyword_id because the term already names its storefront.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource+scope: 'The App Store search results for one term in one storefront, on one day: who ranked, in what order.' It is immediately distinguishable from siblings like get_keywords (tracked term metadata) and get_top_charts (chart rankings).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes between input modes ('pass `keyword_id` for a term you already have an id for, or `keyword` + `country` for words a user typed'), tells when to omit the date, and names the alternative sources of a keyword_id (get_keywords, discover_keywords). It also states a negative: 'It does not track the keyword for your account.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources