microsoft-ads-mcp

delete_ad_group

Delete one or more ad groups from a campaign by providing their unique IDs.

Instructions

Delete one or more ad groups 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": {
      "campaign_id": "<campaign_id>",
      "ad_group_ids": "<ad_group_ids>"
    },
    "name": "delete_ad_group"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes	The parent campaign id.
`ad_group_ids`	Yes	The ad group ids to delete.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`ids`	No
`message`	Yes
`partial_errors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false, implying destruction, and the description says 'delete', which is consistent but adds no additional behavioral context like irreversibility, permissions, or cascading effects.

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?

Extremely concise (6 words), efficient, and front-loaded. However, it could include slightly more context without becoming verbose.

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 simple delete operation, the description lacks important details such as whether the delete is soft or permanent, idempotency, and what the output schema contains. Minimal completeness given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Scema coverage is 100% with clear descriptions for both parameters. The description adds no extra meaning beyond what the schema already provides.

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 tool deletes one or more ad groups by ID, which is specific and distinguishes it from sibling tools like delete_keyword or delete_campaign.

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 on when to use this tool versus alternatives, such as update_ad_group or other operations. No exclusions or context provided.

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

Deploy Server