MCP Apple Ads

Apple Ads: Get Ad Group

apple_ads_get_ad_group

Read-only

Retrieve a single Apple Ads ad group by ID to inspect its bid, pricing model, and targeting settings. Use it to verify ad group configuration before making campaign changes.

Instructions

Get one ad group in full, including its bid, pricing model and targeting.

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": {
      "adGroupId": "<adGroupId>"
    },
    "name": "apple_ads_get_ad_group"
  }
}

Input Schema

Name	Required	Description
`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.
`adGroupId`	Yes	The numeric id of the entity, as returned by the matching list tool.
`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.6/5.0

Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a non-mutating read, so the description's added value is limited to which fields come back ('bid, pricing model and targeting'). It says nothing about behavior when the ad group is missing or inaccessible, and no output schema exists to cover the return shape.

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 front-loaded sentence with no filler; the resource and its returned contents are stated immediately with zero redundant wording.

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 simple single-entity read tool with full schema coverage and a readOnlyHint, the description covers purpose and the general shape of what comes back. The absence of an output schema leaves the exact response fields only loosely sketched, which is a minor gap rather than a blocking one.

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 three parameters are documented in the schema itself, including the savePath and adAccountId resolution rules. The description adds no parameter-level meaning, so baseline 3 applies.

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 pairs the specific verb 'Get' with the resource 'one ad group' and states scope ('in full'), which cleanly separates it from apple_ads_list_ad_groups. It stops short of explicitly naming that sibling, but the singular-resource framing is enough for an agent to distinguish them.

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?

Usage is only implied: fetch a single ad group's details. There is no explicit when-to-use guidance, no prerequisites (e.g. needing an adGroupId obtained from the list tool), and no mention of when to prefer the list tool instead.

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