Apple Ads MCP

targeting_keywords_delete

Remove multiple targeting keywords from an ad group in bulk using their unique IDs.

Instructions

Bulk-delete targeting keywords by ID.

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>",
      "keywordIds": "<keywordIds>"
    },
    "name": "targeting_keywords_delete"
  }
}

Input Schema

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

No annotations are present, and the description only implies a destructive operation. It fails to disclose potential side effects, error behavior, permissions needed, or idempotency—all unsupported by either annotations or description.

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 concise, consisting of a single sentence. It is efficiently written but lacks structure (e.g., sections or bullet points) to improve readability.

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?

For a tool with four parameters and no output schema, the description fails to cover important details such as return values, error handling, prerequisites, or relationships to sibling tools. It is incomplete for an agent to use effectively.

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?

With only 25% schema description coverage and no additional explanation in the description, the meaning of parameters like campaignId and adGroupId remains unclear. The description adds no value beyond the schema's names and types.

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-delete) and resource (targeting keywords by ID), distinguishing it from the sibling 'targeting_keywords_delete_single'. However, it omits the required context of campaign and ad group, which may lead to confusion.

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., 'targeting_keywords_delete_single' or other delete tools). No context for scenarios or exclusions.

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

Deploy Server