Skip to main content
Glama
block-town

google-ads-transparency-mcp

by block-town

Related Servers

Alternatives to google-ads-transparency-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to research competitor ads, analyze advertiser profiles, and compare ad presence across 42 regions using publicly available Google Ads Transparency data.
      5
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Ads API that enables LLMs to search and query Google Ads accounts, retrieve resource metadata, and generate keyword ideas.
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Open-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.
      54
      56 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that provides tools and resources for interacting with Google Ads API, enabling search, metadata retrieval, and account management through natural language.
      3
      929
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for the OpenAI Ads (ChatGPT Ads) Advertiser API, providing tools for agent-led performance marketing such as finding dead ads, auditing near-duplicate copy, and auditing ad-group context hints.
      18
      MIT

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target a distinct operation: searching advertisers, fetching ads, comparing domains, summarizing, and downloading creatives. The main overlap is get_ads vs get_ad_detail (both return decoded ad content) and search_advertiser_by_domain vs compare_advertisers (both do domain lookups), but the descriptions sufficiently distinguish single vs batch and list vs individual.

    Naming Consistency4/5

    The set mostly follows verb_noun snake_case (get_ads, search_advertisers, compare_advertisers, fetch_ad_creative, download_ad_creatives). It is marred by 'advertiser_summary' (noun-style instead of summarize_advertiser) and inconsistent singular/plural in search_advertiser_by_domain vs search_advertisers, but these are minor.

    Tool Count5/5

    8 tools is well-scoped for a Google Ads transparency server; there is no redundancy extreme and each tool earns its place. This falls comfortably in the ideal range for a domain-specific server.

    Completeness4/5

    The surface covers the main user journeys: find an advertiser (keyword/domain/batch compare), inspect their ads (list/detail/summary), and download creatives (single/bulk). Minor gaps like pagination beyond count or filtering ads by date/format exist, but agents can accomplish the core transparency-research tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow