Skip to main content
Glama

google_ads_ads_update_status

Set delivery status of a Google Ads ad to ENABLED, PAUSED, or REMOVED without resetting learning signals. Lightweight update returns ad ID and new status for pause/resume workflows.

Instructions

Sets the delivery status of a single ad to ENABLED, PAUSED, or REMOVED. Lightweight — writes only the status field and does not reset learning signals. Returns the ad ID and new status. Reversible via rollback_apply. Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
ad_group_idYesParent ad group ID.
ad_idYesAd ID.
statusYesTarget status. REMOVED is a soft delete — the ad stops serving but remains queryable by ID.
Behavior5/5

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

Discloses that it is lightweight, only writes the status field, does not reset learning signals, returns the ad ID and new status, and is reversible. No annotations provided, but description adequately covers behavioral traits.

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 sentences covering all essential aspects: purpose, behavioral notes, return value, and sibling differentiation. No unnecessary words.

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

Completeness5/5

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

Given the tool's simplicity and the fact that it returns ad ID and new status as mentioned, the description is complete. No missing critical information for an agent to use it correctly.

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

Parameters4/5

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

All parameters have schema descriptions, and the description adds context about the tool's effect (e.g., REMOVED is a soft delete, no learning signal reset). The description doesn't elaborate on each parameter beyond the schema but provides useful behavioral context.

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?

Clearly states the action: sets delivery status to ENABLED, PAUSED, or REMOVED. Distinguishes itself from sibling tool google_ads_ads_update by specifying that this tool only modifies status, not creative copy.

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 says 'Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.' Also mentions reversibility via rollback_apply, providing clear guidance on when to use this tool.

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/logly/mureo'

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