Skip to main content
Glama
jomiferse

Google Ads MCP Admin

by jomiferse

Related Servers

Alternatives to Google Ads MCP Admin

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      An 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.
      22
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Google Ads MCP server that enables safe, auditable management of ad accounts through natural language, including proposing, reviewing, applying, and rolling back changes with guardrails and dry-runs.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An 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.
      18
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Extends the official Google Ads MCP with a safe write layer for creating paused-by-default Search campaigns and an account auditor, all running locally with no hosted dependencies.
      13
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      MCP server to read and manage Google Ads accounts via GAQL queries, campaign/ad group/keyword operations, and safe write support with draft-confirm flow.
      16
      24
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing Google Ads campaigns through the official Google Ads API, covering accounts, campaigns, budgets, keywords, search terms, and keyword ideas. It provides tools for both reading and mutating live ads data, such as pausing campaigns, updating budgets, and adding keywords.
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool serves a distinct purpose: customer discovery, metadata lookup, data search, and mutation plan lifecycle. The only mild ambiguity is between 'plan_mutations' and 'get_mutation_plan', as both return previews, but their roles (create vs retrieve) are clarified in descriptions.

    Naming Consistency4/5

    Tools follow a consistent [domain]_[action] pattern with snake_case, such as customers_list_accessible_customers and mutations_apply_mutation_plan. The name 'search_search' is slightly awkward (resource and verb identical), but overall the pattern is predictable and coherent.

    Tool Count5/5

    Eight tools is well-scoped for the Google Ads admin domain, covering customer access, metadata/field discovery, search, and a complete mutation planning workflow. No redundant or excessive tools.

    Completeness4/5

    The mutation plan lifecycle is well covered (plan, get, cancel, acknowledge, apply), and search is supported by metadata discovery. Minor gaps include no way to list all mutation plans and no single-customer detail endpoint, but these are edge cases rather than core dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues