Skip to main content
Glama
Sign In
Apple Ads MCP

Apple Ads MCP

by AppVisionOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

campaigns_delete

Permanently remove an Apple Ads campaign by providing its campaign ID. This deletion cannot be undone.

Instructions

Permanently delete a campaign. Cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
campaignIdYes
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.3/5.0
Behavior3/5

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

The description explicitly states the action is permanent and irreversible, which is a key behavioral trait. However, it omits other important behaviors such as cascading effects on child entities, required permissions, or rate limits. With no annotations, more detail is expected.

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 extremely concise, consisting of two well-placed sentences. The action is front-loaded, and the critical behavioral detail (irreversibility) follows immediately. No superfluous 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?

For a destructive operation, the description lacks important context such as what happens to associated adgroups/ads, whether deletion is immediate, or expected return values. Given no output schema, the description should cover these gaps but does not.

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?

The tool description does not mention or explain any parameters. The schema provides description for orgId but not for the required campaignId. With 50% schema coverage, the description fails to compensate by adding parameter context.

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 'delete' and the resource 'campaign', emphasizing permanence. It distinguishes from update or read operations on campaigns and from deletion of other entities like adgroups.

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., pausing a campaign) or prerequisites (e.g., campaign existence, permissions). The description does not mention any context for safe usage.

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