Skip to main content
Glama

google_ads_campaigns_update

Partially update a Google Ads campaign's name or bidding strategy while preserving omitted fields. Supports rollback to restore previous values. For status-only changes, use the dedicated status update tool.

Instructions

Updates one or more settings on an existing campaign. Partial update — only fields provided are changed; omitted fields are preserved. Returns the updated campaign record. Mutating and reversible via rollback_apply (rollback restores the previous field values). For status-only changes (ENABLED / PAUSED / REMOVED) prefer google_ads_campaigns_update_status, which is a lighter-weight call and maps cleanly to pause/resume workflows.

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 to update.
nameNoNew campaign name (max 255 chars).
bidding_strategyNoNew bidding strategy. Switching strategies can reset learning periods — confirm with the operator before changing on an ENABLED campaign.
Behavior4/5

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

Discloses partial update behavior, mutability, reversibility via rollback_apply, and a warning about bidding strategy learning periods. Lacks mention of authentication or rate limits, but adds significant value beyond the absent annotations.

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 well-structured: core action, return and rollback, alternative guidance. No filler words, front-loaded with essential info.

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?

Adequately covers return value and reversibility, and references rollback_apply. Could mention prerequisites or error handling but overall sufficient for a 4-parameter update tool without output schema.

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 already covers all parameters with descriptions (100% coverage). The description adds context on partial update, rollback, and a warning for bidding_strategy, enhancing understanding beyond schema.

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 updates an existing campaign with partial update semantics, and distinguishes from the status-only sibling tool by advising when to use the alternative.

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

Usage Guidelines4/5

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

Provides explicit guidance to prefer the lighter-weight google_ads_campaigns_update_status for status changes, but does not include a hard exclusion or additional when-not scenarios.

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