Skip to main content
Glama
AppVisionOS

Apple Ads MCP

adgroups_delete

Delete an ad group from an Apple Ads campaign by specifying the campaign and ad group IDs.

Instructions

Delete an ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYes
adGroupIdYes
orgIdNoOverride the org (account) for this call. Defaults to ASA_ORG_ID. Use the `org_acls` tool to discover orgIds.
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states 'Delete' but does not elaborate on side effects, irreversibility, permission requirements, or cascading effects on related entities like keywords or creatives.

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

Conciseness2/5

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

While the description is extremely short, it is not effectively concise because it fails to convey any valuable information beyond the tool name. It sacrifices substance for brevity, resulting in a low-value statement.

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 simplicity of the tool (delete a resource by two required IDs) and the absence of an output schema, the description is insufficient. It does not explain the required parameters, the optional override, the response behavior (e.g., success indication), or any prerequisites like having an active campaign.

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 input schema has only 33% field descriptions (only orgId has a description via the schema). The tool description adds no parameter-level information, leaving campaignId and adGroupId completely unexplained when their types and purposes are critical for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete an ad group' is a tautology that merely restates the tool name. It does not provide additional context about the specific operation or distinguish it from sibling tools like adgroups_update or adgroups_get.

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 given on when to use this tool versus alternatives. For example, it does not mention that this deletes a specific ad group within a campaign, nor does it advise against using it without proper authorization or understanding of consequences.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AppVisionOS/apple-search-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server