Skip to main content
Glama
Sign In
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft removing an entity

remove_entity
Destructive

Permanently delete a Google Ads campaign, ad group, ad, keyword, asset, or criterion. Returns a preview plan with a plan_id for confirmation; use pause_entity instead for reversible disabling.

Instructions

Draft REMOVING an entity — returns a PREVIEW. This is IRREVERSIBLE.

Removed entities cannot be re-enabled; pause_entity is the reversible way to temporarily disable something. Returns a preview with a plan_id and requires_double_confirm=true; nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>"
    },
    "name": "remove_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesThe resource ID. campaign / ad_group / asset_group / asset: simple numeric ID. ad: "adGroupId~adId" (a bare ad ID is resolved to its ad group). keyword and ad_group_criterion: "adGroupId~criterionId". negative_keyword and campaign_criterion: "campaignId~criterionId" (the resource_id field from get_negative_keywords). shared_criterion: "sharedSetId~criterionId" (the resource_id field from get_negative_keyword_list_keywords). campaign_asset: "campaignId~assetId~fieldType". ad_group_asset: "adGroupId~assetId~fieldType". customer_asset: "assetId~fieldType".
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
entity_typeYes"campaign", "ad_group", "ad", "keyword", "asset_group", "negative_keyword", "shared_criterion", "campaign_asset", "ad_group_asset", "asset", "customer_asset", "ad_group_criterion", or "campaign_criterion".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.35.1
    • changedInput schema / properties / entity_id / description
      Previous value: -"The resource ID. campaign / ad_group / asset_group / asset: simple numeric\nID. ad: \"adGroupId~adId\" (a bare ad ID is resolved to its ad group).\nkeyword and ad_group_criterion: \"adGroupId~criterionId\".\nnegative_keyword and campaign_criterion: \"campaignId~criterionId\"\n(the resource_id field from get_negative_keywords).\nshared_criterion: \"sharedSetId~criterionId\" (the resource_id field\nfrom get_negative_keyword_list_keywords). campaign_asset:\n\"campaignId~assetId~fieldType\". customer_asset: \"assetId~fieldType\"."New value: +"The resource ID. campaign / ad_group / asset_group / asset: simple numeric\nID. ad: \"adGroupId~adId\" (a bare ad ID is resolved to its ad group).\nkeyword and ad_group_criterion: \"adGroupId~criterionId\".\nnegative_keyword and campaign_criterion: \"campaignId~criterionId\"\n(the resource_id field from get_negative_keywords).\nshared_criterion: \"sharedSetId~criterionId\" (the resource_id field\nfrom get_negative_keyword_list_keywords). campaign_asset:\n\"campaignId~assetId~fieldType\". ad_group_asset:\n\"adGroupId~assetId~fieldType\". customer_asset: \"assetId~fieldType\"."
    • changedInput schema / properties / entity_type / description
      Previous value: -"\"campaign\", \"ad_group\", \"ad\", \"keyword\", \"asset_group\",\n\"negative_keyword\", \"shared_criterion\", \"campaign_asset\", \"asset\",\n\"customer_asset\", \"ad_group_criterion\", or \"campaign_criterion\"."New value: +"\"campaign\", \"ad_group\", \"ad\", \"keyword\", \"asset_group\",\n\"negative_keyword\", \"shared_criterion\", \"campaign_asset\",\n\"ad_group_asset\", \"asset\", \"customer_asset\", \"ad_group_criterion\", or\n\"campaign_criterion\"."
  2. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / entity_id / description
      Added value: +"The resource ID. campaign / ad_group / asset_group / asset: simple numeric\nID. ad: \"adGroupId~adId\" (a bare ad ID is resolved to its ad group).\nkeyword and ad_group_criterion: \"adGroupId~criterionId\".\nnegative_keyword and campaign_criterion: \"campaignId~criterionId\"\n(the resource_id field from get_negative_keywords).\nshared_criterion: \"sharedSetId~criterionId\" (the resource_id field\nfrom get_negative_keyword_list_keywords). campaign_asset:\n\"campaignId~assetId~fieldType\". customer_asset: \"assetId~fieldType\"."
    • addedInput schema / properties / entity_type / description
      Added value: +"\"campaign\", \"ad_group\", \"ad\", \"keyword\", \"asset_group\",\n\"negative_keyword\", \"shared_criterion\", \"campaign_asset\", \"asset\",\n\"customer_asset\", \"ad_group_criterion\", or \"campaign_criterion\"."
  3. First observedv0.9.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavioral facts: the call only drafts, returns a plan_id with requires_double_confirm=true, no state changes until confirm_and_apply, and removal cannot be undone/re-enabled. That sequencing detail is exactly what prevents an agent from misusing a destructive tool.

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?

Three short front-loaded sentences: what it does and that it's irreversible, then the safer alternative, then the confirm workflow. Emphasis on 'PREVIEW' and 'IRREVERSIBLE' puts the highest-risk information first with zero 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?

Output schema exists so return values need no explanation, and the description covers the draft/confirm lifecycle and irreversibility well. It omits that Reddit entities fall under the sibling remove_reddit_entity rather than this tool, a minor routing gap given the very large sibling set.

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%, and the per-entity ID format rules are fully documented in the schema itself. The description adds no meaning about entity_type or entity_id, so the baseline 3 applies — the schema does all the work here.

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 first clause states a specific verb and resource ('Draft REMOVING an entity') and immediately clarifies the scope ('returns a PREVIEW'), which is critical because the name could be read as an immediate deletion. It distinguishes itself from pause_entity and confirm_and_apply by name, so an agent can route correctly without opening any 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?

Explicitly names the alternative ('pause_entity is the reversible way to temporarily disable something') and the exact condition that selects it. It also states the follow-up requirement ('nothing changes until confirm_and_apply applies it'), giving a complete when/when-not/next-step picture.

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