Apple Ads MCP

adgroups_find_in_campaign

Find ad groups in a campaign using a selector to filter by conditions, select fields, and paginate results.

Instructions

Find ad groups within a single campaign using a selector.

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": {
      "campaignId": "<campaignId>",
      "selector": "<selector>"
    },
    "name": "adgroups_find_in_campaign"
  }
}

Input Schema

Name	Required	Description
`campaignId`	Yes
`selector`	Yes	Selector object for /find endpoints. Combine conditions / fields / orderBy / pagination.
`orgId`	No	Override the org (account) for this call. Defaults to ASA_ORG_ID. Use the `org_acls` tool to discover orgIds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the action and scope, but does not disclose behavioral traits such as permissions required, read-only nature, or pagination behavior.

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?

The description is a single sentence, front-loaded with the core purpose, and contains no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the selector object and the lack of an output schema, the description is minimal. It does not explain what fields are filterable, nor does it describe the return type, leaving the agent to infer from the schema.

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 coverage is 67% (descriptions for selector and orgId). The description adds no additional meaning beyond the schema; it only mentions 'using a selector' which is already clear from the schema. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Find', the resource 'ad groups', and the scope 'within a single campaign', which distinguishes it from the sibling tool 'adgroups_find_org_wide' that searches org-wide.

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?

The description implies use when you need ad groups in a specific campaign, but does not provide explicit when-not-to-use guidance or mention alternatives like 'adgroups_find_org_wide' or 'adgroups_list'.

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

Deploy Server