google-ads-agent
Related Servers
Alternatives to google-ads-agent
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceMCP server for Google Ads. Audit spend, find wasted budget, create campaigns, monitor performance, and optimize ads directly from ChatGPT, Claude, or any MCP-compatible client.MIT- FlicenseNot gradedqualityDmaintenanceMCP server that lets any LLM manage Google Ads campaigns from the terminal. Supports read and write operations.-
- AlicenseBqualityBmaintenanceOpen-source MCP server for Google Ads (Meta Ads coming soon) that lets AI assistants manage ad campaigns, reporting, keywords, and targeting in plain English from any MCP client, with safety-first creation of paused campaigns.54187 npm3MIT
- AlicenseAqualityAmaintenanceAn MCP server that provides read and write access to Google Ads, allowing natural language management of campaigns, budgets, ad groups, bids, and keywords, with dry-run validation for safety.18MIT
- AlicenseAqualityAmaintenanceAn MCP server that enables safe, audited mutation of Google Ads campaigns—creating ads, ad groups, keywords, and assets or adjusting budgets and statuses—with a dry-run default and an optional guarded remove operation, plus read-only Keyword Planner ideas.221MIT
- AlicenseAqualityDmaintenanceMCP server for AI agents to manage ad campaigns across Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, and more2151 npm17MIT
TDQS
Scored across 41 tools
Most tools target a distinct resource or action, and the descriptions clearly separate pairs like pause_keywords vs pause_ad_groups and add_negative_keywords vs add_shared_negative_keywords. However, the four performance-variant tools, the preview_campaign/forecast_campaign pair, and the governance tools (policy_status, list_capabilities, explain_capability) require careful reading to pick correctly, and the generic mutate/run_gaql escape hatches broadly overlap with the specific tools.
Almost all tool names are snake_case with an imperative verb first, following a list_/create_/preview_/pause_/remove_/promote_ pattern. The main deviations are the noun-style report tools like keyword_performance, ad_asset_performance, geo_performance, search_terms, and conversion_actions, which are consistent in style but not verb_noun. Overall the naming is predictable and readable.
At 41 tools, this is well over the 25-tool threshold and makes for a heavy selection surface that will consume significant agent context. The broad Google Ads scope justifies much of the breadth, but clusters like the four performance reports, the capability/proposal machinery, and the generic mutate path could be consolidated. It is capable but oversized.
The toolset covers the campaign lifecycle, keyword/ad group/ad operations, negative keywords, drafts, audits, forecasting, performance analysis, and governance, with mutate and run_gaql as escape hatches so there are no dead ends. A few common operations such as pausing/toggling campaigns or creating ad groups are not first-class tools and must go through mutate, and shared-list creation is left to raw API calls. These are workable gaps rather than blocking ones.