MCP Apple Ads

Apple Ads: List Ad Accounts

apple_ads_list_accounts

Read-only

List ad accounts reachable by your API key and the roles you hold, so you can obtain the account ID needed by other ad management tools.

Instructions

List the ad accounts this API key can reach, with the roles it holds on each. This is the bootstrap call: every other tool needs an ad account, and the id here is what to pass as adAccountId or set as APPLE_ADS_AD_ACCOUNT_ID. Also returns the API identity itself. Costs two requests.

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_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only safety, and the description adds real behavioral detail beyond them: the call costs two requests and returns the API identity as well as the account list. It does not address failure modes (invalid key) or whether the account list paginates, which keeps it below a top score.

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?

Three short sentences, front-loaded with the purpose, then the workflow role, then the cost caveat. No redundant restatement of the name or title, and every sentence contributes new information.

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?

There is no output schema, so the description carries the return-value burden and does it: it names the account fields (id, roles) and the additional API identity. For a one-optional-parameter read tool that acts as an entry point, nothing an agent needs to call it 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?

Only one optional parameter, `savePath`, and the schema already documents it at 100% coverage including the parent-directory behavior. The description adds no meaning about the parameter, 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 ad accounts reachable by this API key) plus the extra payload (roles per account). This is distinguishable at a glance from every sibling, which all operate inside an already-known account.

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 frames itself as the bootstrap call that must precede all other tools, and tells the agent exactly how to reuse the returned `id` (as `adAccountId` or APPLE_ADS_AD_ACCOUNT_ID). That is a concrete when-to-use plus a hand-off instruction, not an implied one.

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