MCP Apple Ads

Apple Ads: Get App

apple_ads_get_app

Read-only

Retrieve an app's advertising details by App Store ID, including the locales its product page supports, to verify how Apple treats it as an ad destination.

Instructions

Get an app's advertising details by adamId — what Apple knows about it as an ad destination, including the locales its product page supports.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adamId": "<adamId>"
    },
    "name": "apple_ads_get_app"
  }
}

Input Schema

Name	Required	Description
`adamId`	Yes	The App Store app id (adamId), e.g. 1234567890. Identical to the app's `id` in App Store Connect (from app_store_connect_list_apps, if that server is loaded) and to the digits in its App Store URL — NOT its bundle id.
`savePath`	No	Absolute path to also write this result to, as pretty-printed JSON. Use it rather than copying values out of the response into a file by hand. Parent directories are created.
`adAccountId`	No	The ad account to act on. Omit it when you have exactly one or APPLE_ADS_AD_ACCOUNT_ID is set — it is resolved automatically. List them with apple_ads_list_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe lookup, so the description's remaining job is to characterize the payload, and it does so only partially by naming the locale/product-page info. Nothing is said about behavior when the adamId doesn't exist or isn't an advertisable destination, which is the main failure mode for a lookup keyed on a caller-supplied id.

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

Conciseness5/5

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

A single em-dash-joined sentence that front-loads the verb, the key, and then the payoff. No filler, no restatement of the title.

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

Completeness4/5

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

For a three-parameter read with no output schema, the definition covers the lookup key, the account resolution note lives in the schema, and the description hints at the return content (locale support). A brief note on result shape or missing-app behavior would close the remaining gap.

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 coverage is 100% and the param descriptions are already rich (adamId disambiguated from bundle id, savePath behavior, adAccountId resolution). The description only restates that the lookup is keyed by adamId, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 and resource ('Get an app's advertising details by adamId') and then defines what those details are ('what Apple knows about it as an ad destination, including the locales its product page supports'). That framing separates it cleanly from apple_ads_search_apps (discovery) and from the campaign/ad-group getters.

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

Usage Guidelines3/5

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

The 'by adamId' phrasing implies you need an id already in hand, and the schema notes point at app_store_connect_list_apps and the App Store URL as sources. But the description never explicitly says when to use this versus apple_ads_search_apps or why you'd want the locale data.

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