MCP Apple Ads

Apple Ads: List Ad Groups

apple_ads_list_ad_groups

Read-only

List ad groups for an Apple Ads account, optionally narrowed to one campaign, so you can inspect the keywords, default bid, and audience refinement each group contains.

Instructions

List ad groups, optionally filtered to one campaign. An ad group holds the keywords, the default bid and the audience refinement; the budget lives on its campaign. Spend and performance come from apple_ads_get_report, not from here.

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

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.
`campaignId`	No	Only ad groups in this campaign.
`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.0

Behavior4/5

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

The readOnlyHint already establishes this as a safe read operation, and the description adds meaningful domain context about what an ad group contains and where budget and performance data live. It does not describe return shape or pagination behavior, but the schema covers paging parameters and the annotation covers safety.

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 core list operation and followed by domain context and sibling routing. Every sentence carries useful information, and nothing is redundant.

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 read-only list tool with full schema coverage and no output schema, the description covers purpose, filtering, domain semantics, and report routing adequately. It could still mention the single-ad-group alternative or expected result structure, but no critical information is missing for correct invocation.

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 the schema already documents all five parameters, including campaignId, limit, offset, savePath, and adAccountId. The description reinforces campaign filtering but adds no syntax, format, or edge-case detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: list ad groups, optionally filtered to one campaign. It also clarifies domain structure by saying the ad group holds keywords, default bid, and audience refinement while budget stays on the campaign. It does not explicitly distinguish itself from apple_ads_get_ad_group, but the purpose is otherwise clear.

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?

It states the optional campaign filter and explicitly routes spend and performance queries to apple_ads_get_report rather than this tool. That is a useful when-not condition. It does not say when to use apple_ads_get_ad_group instead of this list tool, leaving one sibling comparison implicit.

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