AppTail – ASO & Keyword Research

Get Account

get_account

Read-only

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 customer sees in the console.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`include_hidden`	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 false for just the working portfolio.
`include_competitors`	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 questions about them.

Output Schema

TableJSON Schema

Name	Required	Description
`apps`	Yes	The account's apps. `app_id` here is what every other tool takes; the numeric id in an App Store URL is `apple_app_id` and will not work.
`plan`	Yes	The plan and its ceilings, read from the services that enforce them — so a refusal cannot disagree with this. Tell the user what was capped rather than working around a limit.
`count`	Yes	Number of apps returned.
`connection`	Yes	App Store Connect health for the account. A `failed` or `stale` connection looks exactly like a quiet fortnight in the numbers, which is why it is stated separately rather than left to be inferred. `none` means Apple has never been connected — impressions, page views, downloads and proceeds do not exist for this account and never did, so say that rather than reporting a decline; everything AppTail crawls itself (ranks, charts, reviews, ratings, releases, prices, markets) works exactly as it does for anybody else. `pending` is the same absence with a connection already on its way: repeat the wait, not the setup instructions.
`data_through`	No	Most recent day App Store Connect reported anywhere in the account. Per-app dates are on each app, and they differ — one healthy app keeps this recent while another has been silent for weeks.
`focus_countries`	Yes	The storefronts this account actually watches, in its own order. Every console screen narrows to these. Narrow your answers to them too unless the user asks otherwise — an answer across all 122 storefronts buries the one they wanted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it discloses that plan limits can refuse a write, that first-party data has a freshness dimension, and that hidden apps must be excluded from portfolio totals to keep answers consistent with the customer's console.

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?

Two sentences, front-loaded with the returned payload before the routing instruction. The first sentence is a dense enumeration but every item earns its place; no filler or repetition.

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?

An output schema exists, so return-shape explanation is unnecessary, yet the description still covers payload scope, the must-call-first routing role, and the consistency caveats. Nothing an agent needs to call this correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100% and both booleans are documented with defaults and rationale, so the schema carries the burden. The description mentions hidden apps and focus storefronts but adds no syntax, default, or format detail beyond what the schema already provides; baseline 3 is appropriate.

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?

States a specific verb+resource (get the account) and enumerates the payload: apps with Apptail ids, plan/limits, ASC health, data freshness, focus storefronts. It explicitly distinguishes itself from every sibling by noting that all other tools require an app_id obtained here.

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?

Gives an explicit routing rule — 'Call this first whenever the request is about "my app" or "my keywords"' — plus the reason (every other tool needs an app_id). It also flags that focus countries and hidden apps must be honored for answers to match the console, which is actionable invocation guidance.

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

All AppTail – ASO & Keyword Research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?