How to integrate Google Ads MCP with OpenAI Agents SDK

Connect OpenAI Agents SDK to Google Ads MCP. Create a new customer list for holiday campaigns, get campaign details by campaign id, and more using natural language, with authentication handled for you.

Google Ads logoGoogle Ads
Oauth2

Google Ads is Google's online advertising platform for creating, managing, and optimizing digital campaigns. It helps businesses reach targeted customers and maximize return on ad spend.

78 Tools

Introduction

This guide walks you through connecting Google Ads to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Google Ads agent that can create and update campaigns and ads, research keyword ideas, run GAQL reports, upload conversions, and manage customer lists through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Google Ads account through Composio's Google Ads MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Google Ads with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Google Ads
  • Configure an AI agent that can use Google Ads as a tool
  • Run a live chat session where you can ask the agent to perform Google Ads operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

What is the Google Ads MCP server, and what's possible with it?

The Google Ads MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Ads account. It provides structured and secure access to your advertising data, so your agent can perform actions like creating customer lists, retrieving campaign details, and managing audience segments on your behalf.

  • Automated customer list creation: Instantly have your agent create new customer lists for targeted marketing campaigns, streamlining your segmentation workflows.
  • Campaign insights by ID or name: Let your agent fetch detailed information for any ad campaign using its ID or name, making reporting and optimization a breeze.
  • Customer list management: Ask your agent to retrieve and review all your existing customer lists, so you always know who you're targeting.
  • Add or remove contacts from lists: Seamlessly update audience membership by having your agent add or remove contacts from specified customer lists for more dynamic targeting.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Google Ads project
  • Some knowledge of Python or Typescript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Google Ads.
6

Set up the Composio instance

dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for Google Ads
const session = await composio.create(userId as string, {
  toolkits: ['googleads'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only googleads.
  • The router checks the user's Google Ads connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Google Ads.
  • This approach keeps things lightweight and lets the agent request Google Ads tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Google Ads. Help users perform Google Ads operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Google Ads and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute Google Ads operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize Google Ads.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Google Ads and OpenAI Agents SDK:

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['googleads'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Google Ads. Help users perform Google Ads operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});

Conclusion

This was a starter code for integrating Google Ads MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Google Ads.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Google Ads action and event your agent gets out of the box.

Add or remove to customer list

Submit email contacts for addition to or removal from a Google Ads Customer Match list through an asynchronous offline user data job, marking ad user data and personalization consent as granted.

Batch Mutate Google Ads Resources

Create, update, remove, or act on supported Google Ads resource types in one request.

Create Callout Asset

Create an immutable account asset containing a validated callout.

Create Customer Client

Create a new Google Ads client under an eligible direct parent manager.

Create customer list

Creates a Google Ads Customer Match user list for contact information, not a customer account.

Create data manager user list

Create a Data Manager user list, or validate without creating one.

Create Experiment

Create the experiment definition that begins an experiment setup workflow.

Create Experiment Arms

Create two Google Ads experiment arms in one atomic batch: one control and one treatment arm belonging to the same experiment.

Delete data manager user list

Delete a Data Manager user list, optionally validating only.

End Experiment

Immediately stop a running experiment without deleting its campaigns, or validate that operation.

Generate Keyword Forecast Metrics

Forecast clicks, conversions and costs for a hypothetical keyword campaign without creating resources.

Generate Keyword Historical Metrics

Retrieve historical search volumes, competition, and bid metrics for supplied keywords without creating or changing advertising resources.

Generate Keyword Ideas

Generate keyword ideas and planning metrics from exactly one seed form.

Get Campaign By Id

Retrieve a Google Ads campaign's name and status by numeric campaign ID for the specified or connected customer account.

Get campaign by name

Retrieve the first Google Ads campaign matching an exact name for the specified or connected customer account.

Get Conversion Action Tag Snippets

Retrieve provider-generated website or call conversion tag snippets after creating a conversion action.

Get conversion ingestion status

Retrieve one Data Manager ingestion status snapshot.

Get customer lists

List a page of Google Ads customer lists (audience and remarketing user segments), not Google Ads accounts.

Get data manager user list

Get one Data Manager user list without modifying it.

Get Experiment

Get one Google Ads experiment by resource name or numeric ID.

Get Experiment Arm

Get one Google Ads experiment arm, including draft campaigns.

Get Required Google Ads Report

Run a prominent, bounded Google Ads report template for Customer, Campaign, Ad, Keyword, Search Term, Dynamic Search Ads Search Term, or Bidding Strategy.

Ingest ad events

Upload ad events for an allowlisted Data Partner to Google Analytics, not Ads.

Ingest audience members

Validate or asynchronously ingest Data Manager audience members.

Ingest conversion events

Validate or submit a bounded Google Ads conversion-event batch.

Ingest users

Ingest account-level identity linkage, not audience-list membership.

List Accessible Customers

List Google Ads customer resource names directly accessible to the authenticated OAuth user.

List data manager conversion actions

List conversion actions usable as Google Ads Data Manager destinations.

List data manager user lists

List one page of Data Manager user lists and their lifecycle configuration.

List Experiment Arms

List Google Ads experiment arms, including draft campaigns.

List Experiments

List Google Ads experiments, optionally filtered by status and type.

List Sub Accounts

List direct child/sub-accounts under a Google Ads manager (MCC) account.

Mutate Ad Group Ads

Create, update, or remove ads in Google Ads ad groups, including responsive search ads.

Mutate Ad Group Assets

Create, update, or remove links between assets and ad groups.

Mutate Ad Group Bid Modifiers

Create, update, or remove ad group bid modifiers, such as device bid adjustments or hotel-specific bid modifier criteria.

Mutate Ad Group Criteria

Create, update, or remove Google Ads ad group criteria in a batch, including keywords, audiences, demographics, mobile apps, YouTube placements, topics, webpages, and Shopping listing groups.

Mutate Ad Groups

Create, update, or remove ad groups within Google Ads campaigns.

Mutate Ads

Update existing Google Ads ad creative fields.

Mutate Asset Group Assets

Create, update, or remove links between assets and Performance Max asset groups.

Mutate Asset Groups

Create, update, or remove Google Ads asset groups for Performance Max campaigns.

Mutate Assets

Create or update supported Google Ads assets such as sitelinks, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets.

Mutate Asset Sets

Create, update, or remove Google Ads asset sets, which group assets for feeds, locations, and other campaign uses.

Mutate Audiences

Create or update Google Ads audiences combining segment attributes.

Mutate Bidding Strategies

Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, and Target Impression Share.

Mutate Campaign Assets

Create, update, or remove links between assets and campaigns.

Mutate Campaign Budgets

Create, update, or remove Google Ads campaign budgets.

Mutate Campaign Criteria

Create, update, or remove campaign-level targeting criteria such as locations, languages, campaign-level negative keywords, devices, schedules, audiences, and IP exclusions.

Mutate Campaign Labels

Create or remove relationships between campaigns and labels.

Mutate Campaigns

Create, update, or remove Google Ads campaigns in a batch; removal is irreversible and validate-only can check changes before applying them.

Mutate Campaigns V2

Create, update, or remove Search and Display Google Ads campaigns in a batch; new campaigns default to paused when status is omitted.

Mutate Conversion Actions

Create, update, or remove Google Ads conversion actions for conversion tracking configuration.

Mutate Custom Audiences

Create, update, or remove Google Ads custom audiences used to reach users by interests, searches, visited URLs, place categories, or installed apps.

Mutate Customer

Update one Google Ads customer's mutable account settings using CustomerService.

Mutate Customer Assets

Create or remove customer-level asset associations.

Mutate Keyword Plan Ad Group Keywords

Create, update, or remove Google Ads Keyword Planner ad group keywords.

Mutate Keyword Plan Ad Groups

Create, update, or remove Google Ads Keyword Planner ad groups.

Mutate Keyword Plan Campaign Keywords

Create, update, or remove negative keywords in Keyword Plan campaigns.

Mutate Keyword Plan Campaigns

Create, update, or remove campaigns in an existing Keyword Plan.

Mutate Keyword Plans

Create, update, or remove saved Google Ads Keyword Planner plans.

Mutate Labels

Create, update, or remove Google Ads labels.

Mutate Portfolio Bidding Strategies

Create, edit, or remove typed Target CPA and Target ROAS portfolio strategies.

Mutate Shared Criteria

Create or remove criteria in a Google Ads shared set, such as negative keywords or excluded placements shared across campaigns.

Mutate Shared Sets

Create, update, or remove Google Ads shared sets used to group shared criteria, such as negative keyword lists, for reuse across campaigns.

Mutate User Lists

Create, update, or remove general Google Ads user-list resources used for audience targeting and remarketing.

Remove all audience members

Validate or asynchronously remove all members of Data Manager audiences.

Remove audience members

Remove specific users from Data Manager audience destinations.

Remove users

Remove users identified by hashed user data from Data Manager destinations.

Schedule Experiment

Schedule a Google Ads experiment and return its long-running operation.

Search GAQL

Run one page of a GAQL search and return its continuation token.

Search Google Ads Fields

Search the Google Ads v26 field metadata catalog with GAQL.

Search Stream GAQL

Execute a Google Ads Query Language (GAQL) query and aggregate every streamed response batch in order.

Update data manager user list

Update mutable Data Manager user-list metadata, optionally validating only.

Update Experiment

Update mutable fields on one Google Ads experiment.

Update Experiment Arms

Update one or more Google Ads experiment arms.

Upload Call Conversions

Upload offline call conversions to Google Ads, or validate them without uploading using validate_only.

Upload Click Conversions

Upload offline click conversions with optional enhanced-conversion identifiers, consent, and cart data.

Upload Conversion Adjustments

Upload retractions, restatements, or enhancements of existing conversions.

Upload User Data

Append or remove already-hashed user data in a Google Ads Customer Match list.

FAQ

Frequently asked questions

With a standalone Google Ads MCP server, the agents and LLMs can only access a fixed set of Google Ads tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Ads and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. OpenAI Agents SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Ads tools.

Yes, absolutely. You can configure which Google Ads scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Ads data and credentials are handled as safely as possible.

Start with Google Ads.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Ads tool your agent needs.Free to start.

Start building