An AI assistant can do useful work in Google Ads, but “connected” does not mean “allowed to do everything.” The real capability is the intersection of four things: the tools exposed by the connected MCP server, the Google Ads access of the signed-in identity, the rules of the target resource, and the instruction you give the assistant.
That distinction matters. The same assistant may be able to report on search terms, create a paused Search campaign, and update a conversion goal – yet be unable to change billing, invite a user, appeal a policy decision, install a website tag, or act in an account outside the signed-in hierarchy.
This guide maps the current HireOtto surface for Google Ads. It is a dated reference, not a promise that every AI client or MCP server supports the same actions.
The short answer
With HireOtto, an AI assistant can read account structure and performance data; run keyword research and account reviews; create supported campaign types and entities; update many settings, assets, budgets, bidding strategies, conversion actions, and goals; and remove a limited set of objects when that operation is explicitly supported.
It cannot assume permission, bypass Google Ads roles, or perform arbitrary interface actions. Some workflows are read-only, some require an Agency plan, some removal actions are irreversible, and Google Ads can still reject a valid-looking request because of policy, object state, or API constraints.
Why Google Ads access is not one switch
1. The AI client
ChatGPT, Claude, or another MCP-compatible client receives your instruction and decides which available tool to call. The client is not the source of Google Ads authority.
2. The MCP server
The server defines the actual tool catalog: which reports, campaign types, settings, and mutations are exposed. Two servers connected to the same Google Ads account can have very different capabilities.
3. The connected Google identity
Google Ads applies the user’s role and manager-account hierarchy. Read-only access supports viewing and reporting, while Standard or Admin access is generally required for campaign edits. Administrative tasks such as managing users or product links require Admin access – and may not be exposed by the MCP server at all.
4. The target object and operation
Google Ads mutations are resource-specific. Create, update, and remove are separate operations, and support for one does not imply support for the others. Validate-only checks and partial-failure behavior also vary by workflow.
The practical rule: treat every requested change as a specific object, field, and operation – not as a blanket permission to “manage Google Ads.”
HireOtto capability matrix
The table below describes the currently documented HireOtto tool surface. “Can change” means the operation is exposed when the connected account, plan, object state, and Google Ads API all allow it.
Area | Can read | Can change | Important limits |
Accounts & structure | Accessible customers, campaign structure, account and campaign settings. | No user, manager-link, billing, or payment administration. | Effective access follows the signed-in role and manager hierarchy. Discovery is one direct manager level at a time. |
Reporting & exports | Campaign, ad group, ad, keyword, search-term, DSA, geo, device, impression-share, conversion, demographic, asset, and Performance Max reporting. | Report configuration only; reporting does not itself mutate campaigns. | Custom GAQL and some exports or advanced views depend on plan and supported fields. |
Keyword research | Keyword ideas, forecasts, historical metrics, and related planning inputs. | Use research outputs to create supported keywords or negatives in a separate approved step. | Forecasts are estimates, not performance guarantees. |
Account reviews | Daily operations, weekly optimization, and account-health audit findings. | No direct changes from the audit workflows. | Formal audits are read-only and Agency-only; a candidate is not an action. |
Search campaigns | Settings, budgets, targeting, bidding, ads, ad groups, keywords, and negative lists. | Create campaigns paused by default; update supported campaign and entity settings; create or update RSAs. | Google may reject policy-ineligible or incompatible settings. Campaign removal is not a documented general operation. |
Ads, ad groups & keywords | Existing entities, status, text, URLs, bids, and related settings. | Create and update supported entities; set supported statuses. Selected ad removal is irreversible. | Confirm IDs and current values. Not every field or ad format is exposed. |
Negative keywords & lists | Shared lists, campaign links, and list contents. | Create lists and items, link or unlink campaigns, and remove supported items. | Match type and scope matter; removal should use exact IDs. |
Dynamic Search Ads | DSA campaigns, settings, page feeds, targets, and ads. | Create and update DSA entities, page feeds, and targeting conditions. | Page-feed and domain rules must be valid for the campaign. |
Performance Max | Campaign, asset-group, asset, signal, search-theme, and performance data. | Create campaigns and supported asset groups; update assets, signals, themes, and selected statuses or removals. | Creative, policy, and object-state requirements still apply; use readback after changes. |
App & Demand Gen | Supported campaign, ad group, ad, asset, and targeting settings. | Create and update supported App and Demand Gen campaigns and entities. | Available fields vary by subtype; Google validation and policy rules remain authoritative. |
Assets & customizers | Extension assets, links, ad customizers, and current associations. | Create, reuse, link, update, and unlink supported assets and customizers. | Support is type-specific; existing assets may be reusable instead of duplicated. |
Budgets & bidding | Campaign budgets, shared budgets, bidding strategies, and assignments. | Create or update supported budgets and portfolio strategies; remove selected unused objects. | Removing shared resources can affect multiple campaigns; check assignments first. |
Conversions | Conversion actions, goal configuration, campaign assignments, and biddable state. | Create or update supported actions and goals; assign, remove, or reset supported goal configurations. | Does not install a website tag, verify firing, or upload offline conversions. |
URL tracking | Campaign tracking templates, final URL suffixes, and custom parameters. | Update supported campaign-level URL tracking settings. | Account-level custom parameters are not currently supported. |
Change history | Recorded Google Ads changes, actor, resource, and time details. | No edits through change-history tools. | Use after a write for verification; availability follows Google Ads retention and API behavior. |
Validation & execution | Current object state, resource IDs, and returned Google Ads errors. | Run supported mutations, including validate-only where exposed. | Every mutate request targets one customer. Approval is a workflow discipline, not a universal server-side gate. |
What the assistant should not claim it can do
The following actions are outside the currently documented HireOtto surface or require a separate system. Treat them as unsupported unless the documentation changes:
Manage Google Ads users, invitations, manager links, billing, or payments.
Appeal policy decisions or guarantee that Google will approve an ad, asset, or campaign.
Install or verify a website conversion tag. Creating a conversion action in Google Ads does not install code on the site.
Upload offline conversions through the current conversion-action workflow.
Set account-level custom parameters; current URL-tracking support is campaign-level.
Change any arbitrary Google Ads field simply because it exists in the interface or API.
Run continuously or optimize autonomously after the conversation ends. HireOtto is a permission-bound tool server, not an autonomous ad manager.
Removal deserves extra caution. HireOtto documents removal for specific objects, including certain ads, negative-list items, custom goals, unused budgets, portfolio strategies, and some Performance Max entities. Do not generalize that into a universal delete capability. Where removal is supported, confirm the exact entity ID and understand whether the action is irreversible.
A safe workflow for AI-assisted Google Ads changes
Confirm the target. State the customer ID, manager context, and the specific campaign, ad group, asset, goal, or other entity.
Read the live state. Ask the assistant to retrieve the current value and exact resource IDs before proposing a change.
Request an explicit diff. Require a clear current-versus-proposed summary, including every field that will change.
Validate when available. Use validate-only behavior to check a supported mutation without committing it.
Approve deliberately. Separate analysis from execution, and approve the exact change rather than a broad optimization goal.
Apply one class of change. Smaller batches make policy failures, partial failures, and unintended edits easier to isolate.
Verify the result. Read the object back and, when useful, check change history to confirm what Google Ads recorded.
A reusable prompt:
For Google Ads customer [CUSTOMER ID], first list what you can read and what you can change for this task. Separate read-only actions, supported writes, and unsupported or unknown actions. Before any write, show the exact entity IDs, current values, and proposed values. Do not execute until I approve. After execution, read the objects back and summarize the result.How HireOtto helps with this workflow
HireOtto gives an MCP-compatible AI client a hosted, OAuth-connected Google Ads toolset. It can help you discover accessible accounts, retrieve structured reports, investigate search terms and performance, run keyword research, review account health, and prepare supported campaign or entity changes without manually navigating each Google Ads screen.
For execution, HireOtto can create and update supported Search, Dynamic Search, Performance Max, App, and Demand Gen workflows; work with ads, ad groups, keywords, negative lists, assets, budgets, bidding strategies, conversion actions, conversion goals, and campaign URL tracking; and read changes back for verification. The assistant should still pause at the human review gate for consequential edits. Google’s permissions, policy checks, resource state, and API rules remain authoritative.
Important limits: formal daily, weekly, and account-health audits are read-only and Agency-only. Multiple Google-profile connections are also Agency-only. Account discovery covers the signed-in account and one manager level below it; a nested manager account may require a separate login with direct access.
See the HireOtto Google Ads MCP tools reference, review authentication and account access, then follow the quickstart to connect your AI client.
How to evaluate another Google Ads AI assistant
Do not stop at “read/write access.” Ask for an evidence-backed matrix with four columns: what it can read, what it can create, what it can update or remove, and what it does not support. Then verify five details:
Which campaign types and resource families are covered?
Which operations are read-only, and which can mutate live accounts?
Does it show exact customer and entity IDs before a write?
Can it validate, read back, and surface Google Ads errors?
Which permissions, plan limits, and manager-account boundaries apply?
A credible answer should be dated and linked to current documentation. “Full access” without an object-level capability list is not a useful specification.
Frequently asked questions
Can ChatGPT change Google Ads campaigns?
Yes – when ChatGPT is connected to a server such as HireOtto that exposes supported write tools, and the authenticated Google Ads user has sufficient access. ChatGPT alone does not have Google Ads authority.
Can an AI assistant delete a Google Ads campaign?
Do not assume so. Removal is resource-specific. HireOtto documents removal for selected entities, but its campaign-settings workflow documents pausing and enabling campaigns rather than universal campaign deletion.
Does OAuth mean the assistant can do everything in the account?
No. OAuth authorizes the connection, but effective access still depends on the user’s Google Ads role, manager hierarchy, the server’s exposed tools, and the requested resource operation.
Can the assistant create conversion tracking?
It can create or update supported conversion actions and goals in Google Ads. That does not install a tag on your site, verify firing, or upload offline conversions. Those require separate implementation and validation workflows.
Can it optimize campaigns automatically?
It can analyze data and execute supported changes you request, but HireOtto is not an autonomous, always-on optimization agent. Keep material changes behind a human approval step and verify the result.
About Me
I’m Suyash – badminton junkie, ex‑GroupM ad‑ops grunt, first marketer at a B2B SaaS startup, and creator of Hiretto: MCP servers for performance marketers.
My mission: less clicking, more thinking.
Let’s build leverage together.
