Skip to main content
Glama
adrex-ai

adrex-ai

Official
by adrex-ai

google_ads_delete_ad

Permanently delete a Google Ads ad using customer, ad group, and ad IDs. Removes the ad from your account immediately.

Instructions

Permanently remove a Google Ads ad — IRREVERSIBLE

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID to delete
ad_group_idYesAd group ID
customer_idYesGoogle Ads customer/account ID
Behavior4/5

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Permanently remove' and 'IRREVERSIBLE' clearly warn about the destructive and irreversible nature of the operation, which is essential. However, it omits other potential behavioral aspects like auth requirements, rate limits, or side effects, so it is not a 5.

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 a single, concise sentence that front-loads the key action and the critical warning. Every word adds value, with no wasted or redundant information.

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?

For a simple delete operation, the description covers the essential action and the irreversible consequence. With no output schema and a straightforward parameter set, it is sufficiently complete, though it could mention side effects or what happens after deletion.

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?

The input schema descriptions cover all three parameters (ad_id, ad_group_id, customer_id) with clear meanings, giving 100% coverage. The description adds no additional parameter-level detail, so the baseline score of 3 applies.

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 'Permanently remove a Google Ads ad' clearly states the specific action (remove) and resource (ad), distinguishing it from sibling tools like pause/enable and delete operations on other entities. The addition of 'IRREVERSIBLE' reinforces the destructive nature.

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

Usage Guidelines3/5

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

The description implies the tool is for permanent deletion of an ad, but it does not explicitly state when to use it versus alternatives such as google_ads_pause_ad or google_ads_enable_ad. There are no exclusions or references to other tools, leaving usage context largely implied.

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/adrex-ai/adrex-ai'

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