Google released version 0.0.6 of its open-source Ads MCP server on November 2, 2026, adding four write-capable tools. The update lets AI assistants create assets, upload videos and manage labels, but it still cannot modify budgets, bids or keywords, leaving core spend controls untouched.
What happened
Google rolled out version 0.0.6 of its open-source Google Ads MCP server on November 2, 2026. The release introduced four new write tools, create_asset, upload_video_asset, manage_labels and manage_label_associations, each protected by a two-step dry-run and checksum flow. The tools are enabled by default, even though the official developer guide, last updated on October 30, still describes the server as “strictly read-only.”
The server now supports creating text, image, video, sitelink, callout and structured snippet assets, uploading local video files to YouTube, and full label management across accounts, campaigns, ad groups and criteria. Image assets accept PNG, JPEG and GIF up to 20 MB, while video uploads handle 11 formats but run only in local mode and default to an unlisted privacy setting.
Despite these additions, the server continues to block any changes to campaigns, budgets, bids or keywords. Those core advertising controls remain read-only, meaning agencies and in-house teams cannot adjust spend through the MCP interface.
Why it matters
The new write capabilities expand what AI assistants can do with Google Ads accounts. Asset creation and video uploads can be automated, reducing manual effort for creative teams. Label management also becomes programmable, allowing dynamic organization of accounts and campaigns.
However, the inability to modify budgets or bids limits the usefulness of the server for full-funnel automation. Marketers looking to let AI optimise spend in real time still need to rely on the traditional Google Ads API or UI. The mismatch between the updated capabilities and the outdated “read-only” documentation also creates compliance risk; teams that approved the tool under the assumption it could not write may inadvertently expose accounts to unintended changes.
What this means for marketers
Marketers can now automate asset generation and video uploads directly from AI workflows, speeding up creative production. At the same time, they must keep budgets, bids and keyword settings under manual or separate API control. Organizations should audit their MCP configurations, disable the new write tools if they are not needed, and update internal policies to reflect the server’s mixed read/write nature.
For agencies that rely on AI-first solutions, this development underscores the importance of layered safeguards, validation-only runs, checksums and explicit user confirmation before any change is committed. It also highlights a niche for services like ADFLU’s AI social media marketing, which can use the new asset-creation tools while keeping spend management in a dedicated, auditable system.
"This initial release is read-only, meaning it can be used for reporting and diagnostics but will not make changes to your account," Dean Lukies, Google Ads API team
The bottom line
Google’s MCP server version 0.0.6 adds four write tools that let AI create assets, upload videos and manage labels, but it still cannot change budgets, bids or keywords. The update expands automation possibilities but also introduces a documentation gap and a need for careful configuration. Marketers should embrace the new asset-creation features while keeping spend controls separate and well-guarded.
Sources
- 1.ppc.land