MCP Apple Ads

Apple Ads: List Product Pages

apple_ads_list_product_pages

Read-only

Lists an app's custom product pages available as ad destinations for targeting in Apple Ads campaigns; page content is managed in App Store Connect.

Instructions

List the custom product pages available as ad destinations. These are the SAME pages configured in App Store Connect — app_store_connect_list_versions and the screenshot tools manage their content; this only lists them for targeting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apple_ads_list_product_pages"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many records to return (1-1000). Apple's own maximum page size is 5000.
`adamId`	No	Only product pages for this App Store app id.
`offset`	No	Rows to skip, for paging. The response's `pagination` block says how many exist.
`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

A4.3/5.0

Behavior4/5

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

With readOnlyHint already declaring a safe read, the description adds the non-obvious fact that these are the same objects configured in App Store Connect, preventing an agent from assuming it can mutate page content here. It does not mention pagination behavior, but the schema's offset/limit descriptions already cover that.

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?

Two short sentences, front-loaded with the action and followed by the disambiguating relationship. Nothing is redundant or padded.

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?

A read-only list tool with all five parameters documented, a safety annotation, and an explicit boundary against the App Store Connect siblings — nothing an agent needs to select or call it correctly is missing. No output schema exists, but the pagination reference in the offset parameter covers the return-shape question.

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%, so every parameter (limit, adamId, offset, savePath, adAccountId) is already documented in structured form. The description adds no parameter-level detail such as how adamId scoping interacts with the ad account, 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 ('List the custom product pages available as ad destinations') and immediately clarifies what these pages are, so the agent knows exactly what comes back. It also names the sibling tools (app_store_connect_list_versions, the screenshot tools) that own the same underlying data, which is a real disambiguation.

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

Usage Guidelines4/5

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

Explicitly scopes the tool to targeting ('this only lists them for targeting') and implicitly routes content management to the App Store Connect siblings. It stops short of stating full when-not-to-use conditions or how the returned pages feed into ad creation, so it is clear context rather than complete routing.

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