Skip to main content
Glama
Sign In
Apple Ads MCP

Apple Ads MCP

by AppVisionOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

adgroup_negative_keywords_delete

Bulk remove negative keywords from an ad group by specifying keyword IDs.

Instructions

Bulk-delete ad-group-level negative 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": "adgroup_negative_keywords_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYes
adGroupIdYes
keywordIdsYes
orgIdNoOverride 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.

  1. First observedv0.1.0

TDQS

B3.1/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 for behavioral disclosure. It only states 'bulk-delete' and 'by ID', but omits details like whether deletions are reversible, permissions required, or what becomes of associated data.

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?

A single sentence effectively conveys the core purpose. No redundant words.

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 and low parameter coverage, the description is incomplete. It lacks information about idempotency, error handling, immediate vs. eventual deletion, or what the response contains.

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?

Only 25% of parameters have descriptions in the schema (orgId). The description does not add meaning to the parameters beyond what the schema provides. For example, it doesn't explain how keywordIds are used or the format of campaignId/adGroupId.

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-delete), resource (ad-group-level negative keywords), and method (by ID). It distinguishes this tool from siblings like create, update, find, and list.

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?

The description provides no guidance on when to use this tool versus alternatives, such as targeting_keywords_delete or campaign-level delete. No exclusions or context are mentioned.

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

Deploy Server

Other Tools