Apple Ads MCP

campaign_negative_keywords_create

Bulk create negative keywords for a campaign to prevent ads from showing on irrelevant searches. These keywords apply to all ad groups within the campaign.

Instructions

Bulk-create campaign-level negative keywords (apply across all ad groups).

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>",
      "keywords": "<keywords>"
    },
    "name": "campaign_negative_keywords_create"
  }
}

Input Schema

Name	Required	Description
`campaignId`	Yes
`keywords`	Yes
`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

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action and scope. It does not disclose any behavioral traits such as idempotency, error handling, permission requirements, or side effects. The schema provides some constraints (max 1000), but description adds no behavioral context.

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 that includes the action, resource, and key differentiator. It is front-loaded and contains no extraneous information. Every word contributes to understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, and low parameter coverage, the description covers only the basic purpose and scope. It omits usage guidance, behavioral details, and parameter explanations, leaving significant gaps for an agent to correctly invoke the tool.

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

Parameters2/5

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

Schema description coverage is 33% (only orgId has a description). The description does not explain parameter meanings or usage beyond implying bulk creation. For example, matchType values (BROAD, EXACT) are not semantically described. The description adds minimal value over the schema.

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 action (bulk-create), the resource (campaign-level negative keywords), and distinguishes from ad-group siblings by noting 'apply across all ad groups'. This provides immediate clarity on scope and usage.

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 when to use this tool (for campaign-level negatives) via the phrase 'apply across all ad groups', but does not explicitly state alternatives (e.g., adgroup_negative_keywords_create) or exclude conditions. The context is clear but lacks explicit guidance.

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

Deploy Server