Skip to main content
Glama

google_ads_campaigns_update_status

Pause, resume, or soft-delete a Google Ads campaign by setting its delivery status. Lightweight action that writes only the status field, with reversibility for pause/resume and 30-day undo for removal.

Instructions

Sets the delivery status of a single campaign to ENABLED, PAUSED, or REMOVED. Lightweight — writes only the status field. Returns the campaign ID and new status. Reversible via rollback_apply for ENABLED ↔ PAUSED; REMOVED is a soft delete that can be reversed by setting status back to PAUSED within 30 days. Use this for pause/resume; use google_ads_campaigns_update to change name, bidding, or other settings.

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.
campaign_idYesCampaign ID.
statusYesTarget status. REMOVED is a soft delete — the campaign stops serving and is excluded from most default listings but remains queryable by ID.
Behavior5/5

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

With no annotations, the description covers key behaviors: lightweight (writes only status), return fields, ENABLED↔PAUSED reversibility via rollback_apply, and REMOVED reversal within 30 days. No contradictions.

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?

Four concise sentences, each with distinct information: purpose, scope, returns, reversibility, and sibling differentiation. No 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?

Provides return values and reversal details despite no output schema. Could mention error conditions or permissions, but given simplicity, it's largely sufficient.

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?

Schema covers 100% of parameters with clear descriptions. The description adds value by explaining reversibility per status value and fallback behavior for customer_id, slightly enhancing understanding.

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 sets the delivery status of a single campaign to ENABLED, PAUSED, or REMOVED, which is specific and distinct from siblings like google_ads_campaigns_update that handle other settings.

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?

Explicit guidance: 'Use this for pause/resume; use google_ads_campaigns_update to change name, bidding, or other settings.' Also explains reversibility and soft delete behavior.

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