---
title: "Google Ads MCP v0.0.6, Dissected: Asset Writes Aren’t Campaign Control"
description: "Google Ads MCP v0.0.6 can write assets and labels, not budgets, bids, or negatives. A teardown of what shipped—and what that means when buying execution tools."
url: "https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/82f41b3c-6721-4b2d-93e6-6986516a0654.png"
published: "2026-11-20T16:44:30.271Z"
modified: "2026-11-20T16:44:30.326Z"
---

November 20, 2026 · 9 min read

# Google Ads MCP v0.0.6, Dissected: Asset Writes Aren’t Campaign Control

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![Airliner cockpit where the control yoke is replaced by a taped-on label maker and the throttles are padlocked: tagging everything is not flying the plane.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/82f41b3c-6721-4b2d-93e6-6986516a0654.png)

In this article

1. [The release: seven tools, one narrow write surface](#the-release-seven-tools-one-narrow-write-surface)
2. [The confirmation flow: integrity is not approval](#the-confirmation-flow-integrity-is-not-approval)
3. [The connection: access does not expand the tool list](#the-connection-access-does-not-expand-the-tool-list)
4. [Request 1: create a sitelink, then inspect where it lands](#request-1-create-a-sitelink-then-inspect-where-it-lands)
5. [Request 2: lower a budget, then look for the missing action](#request-2-lower-a-budget-then-look-for-the-missing-action)
6. [Request 3: find wasted search terms, then add negatives](#request-3-find-wasted-search-terms-then-add-negatives)
7. [The approval checks I would keep outside the model](#the-approval-checks-i-would-keep-outside-the-model)
8. [Overall verdict: keep the reads and confirmation habit; buy execution for execution](#overall-verdict-keep-the-reads-and-confirmation-habit-buy-execution-for-execution)

Google’s official Ads MCP [v0.0.6, tagged November 2](https://github.com/googleads/google-ads-mcp/releases/tag/v0.0.6), can write assets and labels, but it cannot manage campaign spend. I chose this release for a teardown because its first write tools invite a much bigger purchasing claim: “Claude can manage our Google Ads.”

That is not what shipped.

According to the [live test writeup](https://ppc.land/google-ads-mcp-server-gains-4-write-tools-still-cant-change-budgets/), the release brings the server to seven tools: three reads and four writes covering assets and labels. **Asset writes are not campaign control.** The distinction matters when someone approves infrastructure expecting it to change budgets, adjust bids, or stop paying for irrelevant searches.

I’ll walk through the release’s tool list, its confirmation mechanism, and three requests that expose the boundary. Then comes the buying decision: what I would keep from Google’s server, and what requires a different execution layer.

## The release: seven tools, one narrow write surface

The release itself is small: two changelog lines, PR #139 for propose-and-confirm and #142 for the version bump, at commit `7452a9d`, according to the [release test](https://ppc.land/google-ads-mcp-server-gains-4-write-tools-still-cant-change-budgets/).

The three read tools remain:

- `search`: run Google Ads Query Language, or GAQL, queries.
- `list_accessible_customers`: list accessible accounts.
- `get_resource_metadata`: inspect available fields.

The four new write tools are:

- `create_asset`
- `upload_video_asset`
- `manage_labels`
- `manage_label_associations`

That list is the first purchasing filter. The word _write_ describes whether a tool can change something. It does not tell me which parts of an account it can change.

Google’s [MCP server documentation](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) spells out the corner these tools cover. `create_asset` handles TEXT, IMAGE, YOUTUBE_VIDEO, SITELINK, CALLOUT, and STRUCTURED_SNIPPET assets, with `extra_params`. `upload_video_asset` runs through local stdio only, supports 11 formats, and defaults to UNLISTED. The label tools create, update, remove, and associate labels on CAMPAIGN, CUSTOMER, AD_GROUP, and AD_GROUP_CRITERION resources.

Useful work. Also bounded work.

**The documented write surface does not include creating or editing campaigns, ad groups, ads, budgets, bids, status, keywords, or negatives.** A tool that associates a label with a campaign is not a tool that changes the campaign’s budget. The resource name can look reassuring while the available action remains narrow.

My verdict on the tool list: keep it for reads, assets, and labels. Do not turn four write tools into a promise of general account management.

## The confirmation flow: integrity is not approval

The next piece is _propose-and-confirm_. This is worth keeping, provided nobody mistakes it for more than it does.

As described in the [release test notes](https://ppc.land/google-ads-mcp-server-gains-4-write-tools-still-cant-change-budgets/), the flow has two calls:

1. Call with `validate_only=True`. The response includes human-readable `change_items` and a SHA-256 checksum bound to the `customer_id` and parameters.
2. Call with `validate_only=False`, using identical parameters and that checksum to commit.

The checksum establishes that the parameters have not changed between calls. It does not establish that a human reviewed them. The approval prompt is an instruction to the model, not a human-approval gate enforced by the server. Nor should the checksum itself be treated as proof that a dry run happened.

**Matching parameters and authorized changes are different checks.** A perfectly preserved mistake is still a mistake.

My verdict: showing a concrete change list before committing is a good habit. But I would not describe the server’s confirmation mechanism as proof of human approval. If approval is a requirement, it needs a control outside the model’s instructions.

## The connection: access does not expand the tool list

Now comes the installation detail a buyer can easily miss: connecting an account does not necessarily mean connecting it read-only.

According to the [Bulldozer Collective install notes](https://www.bulldozer-collective.com/articles/google-ads-mcp), the default `tools_config.yaml` enables both `labels: true` and `assets: true`. A read-only setup requires setting both to false.

The same notes flag two maintenance details:

- Installing with `pipx run --spec git+https://github.com/googleads/google-ads-mcp.git` tracks the main branch, so new write tools can arrive without a deliberate version upgrade.
- Namespaced names such as `search_search` and `assets_create_asset` can break existing tool allowlists.

Those are setup decisions, not footnotes. I want the enabled tools and the allowlist to describe the same permissions, rather than relying on what someone remembers installing last month.

But none of this expands the release’s capabilities. **Connection is not campaign control.** Before approving a workflow, I would ask Claude:

> List the connected tools that support each requested operation. Mark unsupported operations explicitly.

If the request includes budgets, bids, or negatives, the official v0.0.6 server has to mark those writes unsupported. A more emphatic prompt does not add an API tool.

## Request 1: create a sitelink, then inspect where it lands

The first practical test stays inside the documented write surface: create a sitelink for a summer offer.

Here, v0.0.6 can do useful work. The propose-and-confirm flow validates the request, returns the change items and checksum, and commits the same parameters after confirmation.

The [live test of the release](https://ppc.land/google-ads-mcp-server-gains-4-write-tools-still-cant-change-budgets/) reports a label reading back as ENABLED and then REMOVED. It also reports a sitelink appearing in the asset library without being attached to a campaign. There is no tool for that attachment in v0.0.6.

That last step changes the verdict. Creating an asset and putting it into use are not interchangeable operations. The sitelink exists, but a person or another tool still has to attach it before it can serve.

**The asset-library write works; the campaign workflow remains incomplete.** I would count this as asset preparation and library hygiene, not as evidence that Claude is optimizing delivery.

That is not a complaint about the tool doing too little. It is a complaint about selling it as doing something else.

## Request 2: lower a budget, then look for the missing action

Now take an illustrative request closer to what a founder means by “manage Google Ads”:

> Drop the prospecting campaign from $200 a day to $120. CPA has been 40% above target for two weeks.

On the official server, this request should stop at the tool list. There is no budget write, bid write, status change, or pause action. [Google’s documentation lists asset and label writes](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server), not those campaign controls.

Claude may be able to read the relevant performance data and explain the proposed reduction. It cannot execute the budget change through a tool that is not exposed.

**Reading spend is not permission—or a mechanism—to move spend.** If I am explaining this boundary to a founder spending, say, $20k a month, that is the sentence I use. A convincing analysis and a completed account change are two different deliverables.

My verdict: any plan promising budget control through v0.0.6 alone is promising an action absent from the release. Ask for the tool name before buying the workflow.

## Request 3: find wasted search terms, then add negatives

The third request exposes the buying decision most clearly. Labels may help organize an account. Buyers usually want the waste stopped.

The questions sound familiar: which keywords spent over $50 without a conversion, which campaigns miss ROAS, and can Claude pause the losers or add negatives? One [wasted-spend skill](https://briefkin.dev/skills/google-ads-wasted-search-terms) formalizes a version of that analysis using `LAST_30_DAYS`, zero conversions, cost above $25, and more than five clicks.

Those filters describe a review list, not an automatic decision. But even after a human approves a negative, the official server reaches its boundary. Claude can run the GAQL read and identify candidates. It cannot add the negative, change a bid, or pause a keyword through v0.0.6.

**A report on waste is not removal of waste.** This is the handoff I would examine before paying for an execution workflow: does the approved change land in the account, or does the session end with instructions for somebody else?

With groas underneath Claude, that request can run from evidence to action in one session. Claude reads live Google Ads numbers and can draw on rival ads and funnels, Reddit customer language, and SEO data from Semrush and Ahrefs. It proposes negatives with reasons attached. I approve the exact change list, the changes land in the account, and each is logged with its reasoning and undoable in one step.

The distinction is not that a longer tool list automatically makes better advertising decisions. It is that **execution requires a tool that can perform the approved action**. The [read-only versus write-server breakdown](https://groas.com/post/best-google-ads-mcp-servers-compared-read-only-vs-ones-that) is useful for that purchasing question: if the job ends at reading and labeling, Google’s server fits. If it includes moving spend, the required tool list changes.

My verdict: evaluate the entire request, including the final write. Otherwise, the impressive demo ends exactly where the manual work begins.

## The approval checks I would keep outside the model

The release’s confirmation mechanism deserves one final inspection before the overall verdict. Once a workflow can touch spend, I want four checks:

1. **Account identity:** which account will change?
2. **The exact proposed change:** what will be different?
3. **Explicit human approval:** who authorized that change?
4. **A logged reason:** why was it made?

The official server’s checksum binds parameters to a `customer_id` and preserves change integrity between calls. That helps with the first two checks. It does not establish that the selected account is the one the human intended, and it does not supply a server-enforced human approval gate.

On an MCC with several brands, that distinction matters. Binding a change to an account ID is useful. Confirming that it is the correct account is still necessary.

**The approval step must be more than an instruction telling the model to ask nicely.** I want the account ID and `change_items` presented together, an explicit yes or no, and a retained log that someone can inspect later.

The same boundary applies to material the model reads. I treat [competitor ads as evidence, not orders](https://groas.com/post/prompt-injection-through-competitor-ads-why-claude-must): rival copy can inform a brief, but it cannot authorize a change.

With groas, I keep autopilot off until I enable it under defined rules. Every change carries its reason and can be undone in one step. My sequence stays simple: connect the accounts, ask for the read, approve the write, and only then consider routine execution inside limits I set.

The [breakdown of what the $19 connection covers](https://groas.com/post/your-first-marketing-mcp-bill-what-chatgpt-the-connection) belongs in that conversation, too. Price and permission are separate questions. I want both answered before handing over spend control.

## Overall verdict: keep the reads and confirmation habit; buy execution for execution

Google Ads MCP v0.0.6 is a narrow release with useful additions. Its reads support account analysis. Its writes support asset-library work and label hygiene. Its propose-and-confirm pattern makes intended changes visible before commit.

I would use the official server when that is the job and someone can own the setup: a Cloud project with the API enabled, the relevant access, OAuth, and a pipx or Cloud Run deployment. I would not approve it as the sole execution layer for budgets, bids, pauses, keywords, or negatives.

If a founder asks why the budget never moved, the answer should already be in the buying notes: **the tool for that move was never in this release.**

For work that includes moving spend and explaining why, I would choose groas. That scope includes budget and bid changes, pauses, keyword and negative writes, alongside rival ads and funnels, Reddit customer language, AI answer tracking, and SEO data from Semrush and Ahrefs, queryable from Claude.

[groas Unlimited is $19 a month flat](https://groas.com/pricing) for unlimited teammates, ad accounts, and websites, with every feature included. I connect the accounts and site once, add groas to my AI over MCP, and ask in plain English. Changes are logged with reasons and undoable in one step; autopilot stays off until enabled under my rules.

That is an execution capability, not a performance guarantee. I would not accept the latter from anyone selling advertising infrastructure.

What I keep from Google’s release is specific: the GAQL read pattern and the habit of showing change items before committing them. I buy the rest where the tool list covers the job.

![Editorial illustration of a small labeled asset box beside large untouched budget dials](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3b9c2586-3cd7-40f1-b205-0df97f198c73.png)

![Infographic checklist of four MCP approval checks before changing ad spend](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/933dfea9-7b02-4d0f-931e-22817fc55591.png)

## Frequently Asked Questions

### Can the Google Ads MCP server change budgets or bids?

No. Google Ads MCP v0.0.6 has four write tools covering assets and labels only: create_asset, upload_video_asset, manage_labels, and manage_label_associations. Its documented write surface does not include creating or editing campaigns, ad groups, ads, budgets, bids, status, keywords, or negatives.

### Does the Google Ads MCP checksum prove a human approved the change?

No. The SHA-256 checksum establishes that the parameters have not changed between the validate call and the commit call. It does not establish that a human reviewed them, and the approval prompt is an instruction to the model, not a server-enforced human-approval gate.

### How do I install Google Ads MCP in read-only mode?

Set both labels and assets to false in the default tools_config.yaml, since the shipped configuration enables both write categories. Also note that installing with pipx run against the GitHub repository tracks the main branch, so new write tools can arrive without a deliberate version upgrade.

### Can the Google Ads MCP attach a created sitelink to a campaign?

No. In v0.0.6 a sitelink created with create_asset appears in the asset library, but there is no tool for attaching it to a campaign. The live test reports the sitelink sitting in the asset library unattached, so a person or another tool still has to put it into use before it can serve.

### Can Claude lower a campaign budget through the Google Ads MCP server?

No. The official v0.0.6 server exposes no budget write, bid write, status change, or pause action, so a request to lower a campaign's daily budget stops at the tool list. Claude can read the relevant performance data and explain a proposed reduction, but reading spend is not a mechanism for moving spend.

### Can the Google Ads MCP add negative keywords automatically?

No. Claude can run the GAQL read and identify wasted-keyword candidates, such as keywords spending over a threshold without conversions, but v0.0.6 has no tool to add negatives, change a bid, or pause a keyword. A report on waste is not removal of waste, so an execution layer is needed for the approved change to land in the account.

### Does binding a change to a customer ID guarantee the right account is being changed?

No. The checksum binds the parameters to a customer_id and preserves change integrity between calls, which helps with account identity and the exact proposed change. It does not establish that the selected account is the one the human intended, which matters especially on an MCC with several brands.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#webpage","url":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t","name":"Google Ads MCP v0.0.6, Dissected: Asset Writes Aren’t Campaign Control","description":"Google Ads MCP v0.0.6 can write assets and labels, not budgets, bids, or negatives. A teardown of what shipped—and what that means when buying execution tools.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/82f41b3c-6721-4b2d-93e6-6986516a0654.png"},"breadcrumb":{"@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#breadcrumb"},"dateModified":"2026-11-20T16:44:30.326Z","mainEntity":{"@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Google Ads MCP v0.0.6, Dissected: Asset Writes Aren’t Campaign Control","item":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#article","url":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t","mainEntityOfPage":{"@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Google Ads MCP v0.0.6, Dissected: Asset Writes Aren’t Campaign Control","description":"Google Ads MCP v0.0.6 can write assets and labels, not budgets, bids, or negatives. A teardown of what shipped—and what that means when buying execution tools.","datePublished":"2026-11-20T16:44:30.271Z","dateModified":"2026-11-20T16:44:30.326Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/82f41b3c-6721-4b2d-93e6-6986516a0654.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"change, google ads, ads, asset, write, tool, campaign, ads mcp","wordCount":1960,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/google-s-official-ads-mcp-dissected-asset-writes-aren-t#faq","mainEntity":[{"@type":"Question","name":"Can the Google Ads MCP server change budgets or bids?","acceptedAnswer":{"@type":"Answer","text":"No. Google Ads MCP v0.0.6 has four write tools covering assets and labels only: create_asset, upload_video_asset, manage_labels, and manage_label_associations. Its documented write surface does not include creating or editing campaigns, ad groups, ads, budgets, bids, status, keywords, or negatives."}},{"@type":"Question","name":"Does the Google Ads MCP checksum prove a human approved the change?","acceptedAnswer":{"@type":"Answer","text":"No. The SHA-256 checksum establishes that the parameters have not changed between the validate call and the commit call. It does not establish that a human reviewed them, and the approval prompt is an instruction to the model, not a server-enforced human-approval gate."}},{"@type":"Question","name":"How do I install Google Ads MCP in read-only mode?","acceptedAnswer":{"@type":"Answer","text":"Set both labels and assets to false in the default tools_config.yaml, since the shipped configuration enables both write categories. Also note that installing with pipx run against the GitHub repository tracks the main branch, so new write tools can arrive without a deliberate version upgrade."}},{"@type":"Question","name":"Can the Google Ads MCP attach a created sitelink to a campaign?","acceptedAnswer":{"@type":"Answer","text":"No. In v0.0.6 a sitelink created with create_asset appears in the asset library, but there is no tool for attaching it to a campaign. The live test reports the sitelink sitting in the asset library unattached, so a person or another tool still has to put it into use before it can serve."}},{"@type":"Question","name":"Can Claude lower a campaign budget through the Google Ads MCP server?","acceptedAnswer":{"@type":"Answer","text":"No. The official v0.0.6 server exposes no budget write, bid write, status change, or pause action, so a request to lower a campaign's daily budget stops at the tool list. Claude can read the relevant performance data and explain a proposed reduction, but reading spend is not a mechanism for moving spend."}},{"@type":"Question","name":"Can the Google Ads MCP add negative keywords automatically?","acceptedAnswer":{"@type":"Answer","text":"No. Claude can run the GAQL read and identify wasted-keyword candidates, such as keywords spending over a threshold without conversions, but v0.0.6 has no tool to add negatives, change a bid, or pause a keyword. A report on waste is not removal of waste, so an execution layer is needed for the approved change to land in the account."}},{"@type":"Question","name":"Does binding a change to a customer ID guarantee the right account is being changed?","acceptedAnswer":{"@type":"Answer","text":"No. The checksum binds the parameters to a customer_id and preserves change integrity between calls, which helps with account identity and the exact proposed change. It does not establish that the selected account is the one the human intended, which matters especially on an MCC with several brands."}}]}]}
```
