Skip to main content
Google Ads gives your agent access to your connected ad accounts. The agent can list accessible customers, query campaign performance with GAQL, inspect campaigns and customer lists, and perform account updates when you ask it to.

What it does

When Google Ads is enabled on an agent, the agent can automatically call Google Ads APIs as part of its reasoning process. You ask a question or give it a task — the agent decides when and how to use your ad account on your behalf.

Prerequisites

You must have an active Google Ads connection in your workspace before enabling this tool. If no active connection exists, the tool cannot be added.
  1. Go to Integrations for your workspace.
  2. Find Google Ads in the integrations grid.
  3. Click Connect and complete the OAuth flow.
  4. Return to your agent and enable the tool.

Adding the tool to an agent

  1. Open an agent in the editor.
  2. Click the button with the tooltip Add MCP Tool or Sub Agent.
  3. In MCP Tools, click Google Ads. The Google Ads node appears on the canvas.
  4. Click the node to open the Settings panel on the right.
  5. In the Authentication field, select the connected Google Ads account the agent should use.
  6. If no active connection is found, the settings panel shows a warning with a link to Integrations to connect first.

Available actions

Agents can use non-destructive Google Ads actions exposed for your connected account, including:
  • List Accessible Customers
  • List Sub Accounts
  • Get Campaign By Id
  • Get Campaign By Name
  • Get Customer Lists
  • Search Stream GAQL
  • Create or update campaigns, ad groups, budgets, assets, and customer lists when prompted
Google Ads is an agent-only integration — it does not appear as a workflow step.

Use cases

  • Pull campaign performance for the last 7 or 30 days with a GAQL query.
  • List accessible ad accounts before targeting a manager (MCC) child account.
  • Look up a campaign by name or ID for validation or reporting.
  • Add contacts to a customer list or pause campaigns when you describe the change in chat.

Notes

  • The agent uses your connected Google Ads account. Make sure OAuth access covers the customer IDs you expect the agent to use.
  • Manager-account (MCC) setups may require targeting a child customer ID while passing the manager ID as login context; reconnecting alone does not fix permission errors against the wrong account.
  • Google Ads API rate limits apply to agent actions the same as direct API usage.
  • This tool counts as 1 credit per action the agent performs.
  • OAuth may show third-party authorization branding during the connect flow.
See also: Integrations, Creating and Configuring