01
What the Developer Assistant is
Google's Ads developer documentation covers Google Ads API Developer Assistant v4.0.0, a specialized development workflow for engineers using the Google Ads API. Google explicitly says the Assistant is an open-source project and not an official Google product.
The Assistant can answer domain questions, construct GAQL, generate client-library code, inspect schemas, troubleshoot integrations and run controlled read-only reporting. Version 4 moves to a global plugin architecture built around Google Antigravity and Claude Code.
02
Schema grounding and validation
Google Ads API changes frequently and combines GAQL with strongly typed Protobuf resources. The Assistant uses current schema information and deterministic validation to reduce field-combination and version errors that a generic chatbot can easily produce.
Google documents workflows for inspecting objects and enums, resolving MCC hierarchies, troubleshooting conversions, generating reporting queries and exporting read-only results. That is particularly relevant to agencies and marketing-automation teams that repeatedly build around the API.
03
Assistant, agent skills and MCP are different layers
The full v4 Assistant is documented for Google Antigravity and Claude Code. Google separately publishes portable Google Ads API agent skills that can be used in a broader set of compatible coding agents, including Codex and Cursor. Those broader skill claims should not be used to imply that the full v4 Assistant runs identically in every host.
Google also documents a separate Google Ads MCP server for controlled access to account data. Skills provide domain instructions; MCP provides tools for live account access; the Developer Assistant combines a broader development workflow with validation, code generation and diagnostics.
04
Read-only execution and mutate safety
The Assistant can generate code for mutate operations, but Google's documented workflow does not automatically execute those campaign-changing mutations. Developers review and run generated mutation code separately.
That boundary lets teams use natural-language reporting and diagnostics without turning the coding agent into an unrestricted autonomous media buyer. Normal Google Ads API developer tokens, OAuth credentials and customer permissions still apply.
05
Requirements and next steps
Google's current setup documentation requires working Google Ads API access, Python 3.10+ for the default Python path, Git and either the Antigravity CLI or Claude Code with its documented prerequisites. The Assistant itself has no separately documented paid subscription price, although surrounding model and infrastructure costs depend on the chosen environment.
For the practical setup and a safer first GAQL report, continue with the installation guide.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.