Skip to main content
Glama

Remove a Microsoft Advertising ad group

msads_remove_ad_group
DestructiveIdempotent

Permanently delete an ad group, along with its keywords and ads. This cannot be undone and its history stays only in reports. Safety checks: the ad group must already be Paused (use msads_set_status first, so you never delete something that is serving), and confirmName must match the ad group's name exactly. To stop an ad group without losing it, pause it instead. Always run dryRun first: it shows what would be deleted (keyword and ad counts).

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

Input Schema

NameRequiredDescriptionDefault
dryRunNoPreview only. Microsoft has no validate-only mode, so Caybl reads the current value and shows exactly what would change (before and after) without sending anything. Free, and cannot affect spend.
accountIdNoMicrosoft Advertising account id or account number (e.g. 'F123ABCD'), as listed by msads_list_accounts. Only needed when the sign-in can reach more than one account.
adGroupIdYesAd group id, from msads_get_ad_groups.
campaignIdYesCampaign id, from msads_get_campaigns.
confirmNameYesThe ad group's exact name, typed back to confirm the deletion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / adGroupId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / campaignId / pattern
      Added value: +"^\\d+$"
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely structured. The description nevertheless adds real context beyond them: permanence with history surviving only in reports, the Paused-state prerequisite, and the exact-match confirmName gate. It does not describe the response payload or per-item failure behavior, so it is solid but not exhaustive for a destructive operation.

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?

Front-loaded with the destructive outcome, then prerequisites, then the recommended alternative — a sensible order for a dangerous tool. It is slightly dense with nested parentheticals, but every sentence carries actionable information and none are filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers deletion scope, irreversibility, prerequisite state, confirmation requirement, and preview workflow for a 5-parameter destructive tool with full annotations and no output schema. What remains unmentioned — error shapes and what dryRun returns structurally — is minor given the rich schema.

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?

Schema description coverage is 100%, so dryRun, confirmName, adGroupId, and campaignId are already documented well, and the description largely restates the exact-name confirmation. Its only meaningful addition is the concrete preview expectation ('keyword and ad counts') and the instruction to run dryRun first, which is marginal over the schema's own 'shows exactly what would change' wording.

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?

Opens with a specific verb and resource plus blast radius: 'Permanently delete an ad group, along with its keywords and ads.' It also implicitly separates itself from msads_set_status by saying to pause rather than delete, so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use and when-not-to-use guidance with named alternatives: require the ad group to be Paused, name msads_set_status as the prerequisite tool, and offer pausing as the non-destructive path. It also mandates a dryRun-first workflow, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources