Apple Ads MCP

adgroup_negative_keywords_create

Add multiple negative keywords to an ad group to exclude unwanted search terms and refine targeting.

Instructions

Bulk-create negative keywords on an ad group.

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

Input Schema

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

C2.7/5.0

Behavior2/5

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

With no annotations available, the description carries full burden for behavioral disclosure. It only states the action without detailing side effects, authorization requirements, idempotency, or what happens on duplicate entries. For a creation tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence) and front-loaded with the key action. However, it may be overly brief, lacking necessary detail. Every sentence earns its place, but some context is missing.

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 no output schema, no annotations, and low schema coverage, the description is incomplete. It does not explain return values, error handling, rate limits, or any prerequisites. It fails to provide agents with enough context for correct invocation.

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 low (25%: only orgId described). The description adds no additional meaning to parameters beyond the schema. It does not explain the role of campaignId, adGroupId, or the keywords array structure, leaving ambiguity.

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 clearly states the action (bulk-create) and the resource (negative keywords on an ad group). It distinguishes from sibling tools like delete, get, list, and update. However, it could be more specific about the scope (ad group level) and what 'bulk' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., campaign_negative_keywords_create for campaign-level, or targeting_keywords_create). The description does not mention prerequisites, limitations, or scenarios where this tool is appropriate.

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

Deploy Server