Google Ads MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_ADS_CONFIG | Yes | Google Ads API Configuration as an inline JSON string. Must contain: client_id, client_secret, developer_token, refresh_token, and login_customer_id. | |
| GOOGLE_ADS_CUSTOMER_ID | Yes | The Google Ads Customer ID to query (numeric string without dashes). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_campaignsC | Fetch Google Ads campaign performance data |
| get_campaign_detailsC | Get detailed information about a specific campaign |
| get_performance_summaryC | Get overall account performance summary |
| get_top_performersC | Get top performing campaigns by specified metric |
| pause_campaignC | Pause a specific campaign |
| enable_campaignC | Enable/resume a paused campaign |
| update_campaign_budgetC | Update the daily budget for a campaign |
| create_responsive_display_adC | Create a Responsive Display Ad with Ad Controls (e.g., enable video creation) |
| create_conversion_actionC | Create a new Conversion Action (e.g., for website, phone calls) |
| get_conversion_actionsB | List all Conversion Actions for the account |
| export_reportC | Export campaign data to CSV or JSON format |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting specific resources like campaigns, conversion actions, ads, and reports, with clear separation between actions like enable_campaign and pause_campaign. However, get_campaigns and get_campaign_details could potentially be confused as both retrieve campaign data, though their descriptions differentiate them as performance data vs. detailed information.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_conversion_action, get_campaigns, and update_campaign_budget. This uniformity makes the tool set predictable and easy to understand at a glance.
With 11 tools, the server is well-scoped for Google Ads management, covering key operations like campaign control, reporting, and ad creation. This count is reasonable and aligns with the domain's complexity without being overwhelming or insufficient.
The tool set provides strong coverage for core Google Ads workflows, including campaign lifecycle (create, enable, pause, update budget), reporting (export, performance summary), and ad management. A minor gap is the lack of tools for deleting resources or managing ad groups, but agents can likely work around this with the available operations.