Apple Ads MCP

campaigns_update

Update specific campaign fields like status, budget, or targeting. Pass only the fields you want to change and optionally clear geo targeting when updating countries or regions.

Instructions

Update a campaign. Pass only the fields you want to change. Use clearGeoTargetingOnCountryOrRegionChange=true if you change countriesOrRegions.

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>",
      "campaign": "<campaign>"
    },
    "name": "campaigns_update"
  }
}

Input Schema

Name	Required	Description
`campaignId`	Yes
`campaign`	Yes	Partial campaign object — fields you want to update.
`clearGeoTargetingOnCountryOrRegionChange`	No	Set to true if changing countriesOrRegions, to clear ad-group geo targeting.
`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

A4.1/5.0

Behavior3/5

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

No annotations provided, so description bears full burden. It reveals one behavioral detail (clearing ad-group geo targeting on country change) but omits others like mutation side effects, permissions, or reversal. The added detail is helpful but insufficient for a mutation tool with no additional metadata.

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?

Two sentences, no fluff, front-loaded with the action. Every sentence adds distinct value: purpose, partial update pattern, and a critical behavioral flag. Highly efficient.

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?

The tool is complex (nested objects, many fields, no output schema), yet the description is bare. It lacks return value information, error handling hints, prerequisites, or restrictions. The partial update guidance and geo flag help, but overall completeness is minimal for the complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (75%), so baseline is 3. The description adds value by clarifying partial update behavior and the `clearGeoTargetingOnCountryOrRegionChange` parameter's semantics, which is not fully explained in the schema. This goes beyond mere repetition.

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?

Clear verb 'Update' with resource 'a campaign', distinct from siblings like create, delete, get, list. The description explicitly states the action and the resource, leaving no ambiguity.

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?

Provides explicit guidelines: use partial updates ('pass only fields you want to change') and a specific flag for geo targeting changes. While it doesn't list alternatives or exclusions, the guidance is directly actionable and covers a key use case.

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

Deploy Server