Skip to main content
Glama

Google Ads: update campaign settings

update_campaign
DestructiveIdempotent

Updates an existing Google Ads campaign's settings.

search_partners, display_network and geo_target_type change the same
three settings create_campaign sets, so a campaign created earlier, or
created outside this server, can be changed here; PRESENCE targets only
people in the targeted locations. Each is applied only when passed.
languages applies to Performance Max, Display and Video campaigns,
including one created outside this server; a campaign with no language
setting may show to people who use any language.

languages sets exactly the given list: languages the campaign has that
are not in it are removed, missing ones added, and the result reports the
campaign's languages before and after (an empty list means every
language). Read the campaign's current languages first and pass every
language to keep: a language left out of the list is removed. Read them
with search: resource campaign_criterion, fields campaign.id,
campaign_criterion.language.language_constant, conditions campaign.id =
<campaign_id>, campaign_criterion.type = 'LANGUAGE',
campaign_criterion.status != 'REMOVED'. Performance Max uses the setting
on YouTube, Display, Discover and Gmail, not on Google Search.
Search campaigns have no language setting: Google Ads removed it in late
September 2026 and matches Search ads by the language they are written
in, so languages is refused on a Search campaign. Language criteria an
older Search campaign still carries are returned by reads but no longer
used by Google. A languages change and the other campaign settings in the
same call are applied together or not at all; a budget change is a
separate request, sent first.

bidding_strategy_type switches the campaign to a standard bidding
strategy, replacing the one it has (including a portfolio strategy). The
usual fix for a new Search campaign that is not winning auctions on manual
CPC is TARGET_SPEND (Maximize Clicks) with a cpc_bid_ceiling_micros cap.
Supported, by campaign type — anything else is refused before any change:
  SEARCH: MANUAL_CPC, TARGET_SPEND, MAXIMIZE_CONVERSIONS, TARGET_CPA,
    MAXIMIZE_CONVERSION_VALUE, TARGET_ROAS.
  PERFORMANCE_MAX: MAXIMIZE_CONVERSIONS, TARGET_CPA,
    MAXIMIZE_CONVERSION_VALUE, TARGET_ROAS.
Moving to TARGET_SPEND requires cpc_bid_ceiling_micros. Re-sending
TARGET_SPEND without a cap on a campaign already using it keeps the
existing cap; nothing clears a cap. For the conversion strategies a target
left out is cleared (e.g. MAXIMIZE_CONVERSIONS removes a target CPA).

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    campaign_id: The ID of the campaign to update.
    name: New campaign name. Optional.
    budget_amount_micros: New daily budget in micros of the account's currency (10000000 = 10.00: ₹10 on an INR account, $10 on a USD one).
        On a budget shared by several campaigns the new amount applies
        to all of them; the result's budget_shared says how many.
        Optional.
    start_date: New start date in YYYY-MM-DD format. Optional.
    end_date: New end date in YYYY-MM-DD format. Optional.
    search_partners: False stops the campaign serving on the Google Search
        Partners network, True allows it. Optional.
    display_network: False stops the campaign serving on the Google
        Display Network, True allows it. Optional.
    geo_target_type: New positive location targeting. One of: PRESENCE
        (only people in the targeted locations), PRESENCE_OR_INTEREST
        (also people elsewhere who show interest in them), SEARCH_INTEREST.
        Optional.
    bidding_strategy_type: New bidding strategy. One of: MANUAL_CPC,
        TARGET_SPEND (Maximize Clicks), MAXIMIZE_CONVERSIONS, TARGET_CPA
        (Maximize Conversions with a target cost per conversion),
        MAXIMIZE_CONVERSION_VALUE, TARGET_ROAS (Maximize Conversion Value
        with a target return on ad spend). See the list above for which
        campaign types accept which. Optional.
    cpc_bid_ceiling_micros: Maximize Clicks' max CPC cap — the most
        Google may bid for one click — in micros of the account's currency
        (10000000 = 10.00: ₹10 on an INR account, $10 on a USD one). Only
        with TARGET_SPEND; required when moving to it, optional (the
        existing cap is kept) when the campaign already uses it.
    target_cpa_micros: Target cost per conversion in micros of the
        account's currency (10000000 = 10.00: ₹10 on an INR account, $10
        on a USD one). Required with TARGET_CPA, refused otherwise.
    target_roas: Target return on ad spend as a ratio (e.g., 2.0 for
        200%). Required with TARGET_ROAS, refused otherwise.
    languages: Google Ads language codes (e.g. en, hi, es, pt, de, fr,
        ja, zh_CN); sets exactly this list, removing the rest, so pass
        every current language to keep. ["all"]
        removes every language setting. Performance Max (used on YouTube,
        Display, Discover, Gmail; not on Google Search), Display and
        Video campaigns only; refused on Search. Optional.
    over_comfort_ack: The user's own words or reason when they asked for
        a budget above their saved comfort (e.g. "user asked for 6,000/day
        on 2026-09-23"). Recorded with the change by the hosted connector;
        never sent to Google. Optional.

Returns:
    Dictionary with the updated resource names and a confirmation message;
    with languages, also languages: {before, after, changed}; with a
    budget shared by several campaigns, also budget_shared: {campaigns}.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
end_dateNo
languagesNo
start_dateNo
campaign_idYes
customer_idYes
target_roasNo
display_networkNo
geo_target_typeNo
search_partnersNo
over_comfort_ackNo
target_cpa_microsNo
budget_amount_microsNo
bidding_strategy_typeNo
cpc_bid_ceiling_microsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/idempotent/openWorld) by disclosing atomicity ('applied together or not at all'), the destructive semantics of languages (omitted languages are removed, empty list means every language), cap/target clearing rules, and that a shared budget change affects all campaigns. over_comfort_ack being recorded locally and never sent to Google is exactly the kind of side-effect context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and organized by concern, but the length is inflated by repetition: the language-setting semantics are explained in the preamble and again under languages, and the bidding-strategy support matrix appears both in prose and in the parameter entry. The content earns its place; the duplication does not.

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 15 parameters, mutation risk and an output schema, the description covers everything needed: prerequisites for reading current languages, refusal conditions, partial-failure semantics, and how results report before/after languages and shared budget counts. No material gap remains for an agent to call this correctly.

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

Parameters5/5

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

With 0% schema description coverage across 15 parameters, the description carries the full burden and does: micros conversion with currency examples, date format, enums for geo_target_type and bidding_strategy_type, per-strategy parameter requirements (target_cpa_micros, target_roas, cpc_bid_ceiling_micros), and language code format. This is the main reason the tool is usable at all.

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?

Opens with a specific verb and resource ('Updates an existing Google Ads campaign's settings') and names the concrete settings it governs, which separates it from set_campaign_status, set_geo_targets, update_ad_group and create_campaign. An agent can tell what this tool does without opening the schema.

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?

Gives strong conditional guidance: which campaign types accept each bidding strategy, when TARGET_SPEND requires a cap, when targets are cleared, and that a budget change is a separate earlier request. It also points at the read path for current languages. It stops short of explicitly routing whole tasks to siblings (e.g. pausing belongs to set_campaign_status), so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources