MCP Apple Ads

Apple Ads: List Campaigns

apple_ads_list_campaigns

Read-only

List campaigns in an Apple Ads ad account with status, daily budget, and promoted app. Use it to find campaign IDs for follow-up detail or reporting calls.

Instructions

List campaigns in an ad account, with their status, daily budget and the app each promotes. Returns the identifying fields, not the full targeting projection — use apple_ads_get_campaign for one campaign in full. Spend and performance are NOT here: those come from apple_ads_get_report.

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

Input Schema

Name	Required	Description
`limit`	No	How many records to return (1-1000). Apple's own maximum page size is 5000.
`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.5/5.0

Behavior4/5

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

With readOnlyHint already declaring the safety profile, the description adds real value by specifying that the response is a summarized projection rather than the full targeting object. It does not discuss paging behavior (limit maximums, response pagination block), but the schema covers those details.

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 what it does, followed by the two routing exclusions. No filler or restatement of annotations.

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?

For a read-only list tool with a fully described schema, the description covers scope, returned fields, and what it deliberately omits. Nothing needed to invoke 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?

Schema description coverage is 100% and all four parameters (limit, offset, savePath, adAccountId) are documented in the schema. The description adds no parameter-level meaning beyond that, so this sits at the baseline.

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 campaigns in an ad account') plus the concrete fields returned (status, daily budget, promoted app). It explicitly distinguishes itself from apple_ads_get_campaign (single campaign in full) and apple_ads_get_report (spend/performance), so an agent can route without opening any schema.

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?

Names both alternatives and the conditions that select them: use get_campaign for one campaign in full, and get_report for spend/performance. The negative scoping ('NOT here') is exactly the exclusion guidance an agent needs.

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