Skip to main content
Glama
Google Ads Transparency Monitor MCP Server

Google Ads Transparency Monitor MCP Server

Google Ads Transparency Monitor MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Google Ads Transparency Center Scraper by Domain actor on Apify. Give it a company domain or an advertiser name. Each run reads Google's public Ads Transparency Center and returns one row per ad, with the format, first and last shown dates, a creative link, and the ad's page, plus a company summary row with Google's total ad count band.

What's Inside

Related MCP server: google-ads-transparency-mcp

What it does

List the Google ads a company runs. Give a company domain (for example stripe.com) or an advertiser name, or lists of either. You get one row per ad with the advertiser, ad ID, format (text, image, or video), first and last shown dates, a creative link, and the ad's Transparency Center page, plus one summary row per input that says whether the company runs Google ads, how many (Google's own count band, for example 8,000 to 9,000), and in which formats. Rows with no ads, blocked requests, or a changed Google page come back free with a row_status saying so.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-google-ads-transparency-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The get_google_ads tool appears.

Prerequisites

Example prompts

  • "Does notion.so run Google ads? How many, and in which formats?"

  • "Show me the 10 most recent video ads HubSpot ran in the US."

  • "For stripe.com, ramp.com, and brex.com, which ones advertised on Google in the last 30 days?"

Tool

get_google_ads. One tool. Example arguments:

{
  "company_domain": "stripe.com",
  "max_ads": "20",
  "since_days": "90"
}

Inputs

Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults. Give one of company_domain, advertiser_name, domains, or advertiser_names.

Input

Type

Required

Description

company_domain

string

no

A company website domain, for example stripe.com.

advertiser_name

string

no

An advertiser name as Google verifies it, for example Stripe, Inc.

domains

array

no

Several company domains. Up to 500 inputs per run.

advertiser_names

array

no

Several advertiser names.

region

string

no

anywhere, or a two letter country code such as US, GB, DE, or FR. Default anywhere.

formats

array

no

text, image, video. Omit for all formats.

max_ads

string

no

Ad rows per input, 1 to 1000. Default 50.

since_days

string

no

Only ads last shown in this many days; 0 for all. Default 90.

include_summary

string

no

true or false. Default true.

max_charge_usd

string

no

Optional cost cap for the run.

skipCache

string

no

true reads fresh results instead of the free 24 hour cache. Default false.

proxy_mode

string

no

auto, direct, or residential. Default auto.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

ad-found, per ad row returned

$0.002

$0.0019

$0.0018

$0.0017

company-summary, per input with ads

$0.003

$0.00285

$0.0027

$0.00255

apify-actor-start, per run start

$0.0005

$0.0005

$0.0005

$0.0005

Rows with no ads, blocked rows, changed source rows, error rows, and cached rows are free.

Your keys

The actor needs no provider key. It reads Google's public Ads Transparency Center and holds no key of its own. If a run uses the Apify proxy, that traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/google-ads-transparency-monitor

License

MIT. See LICENSE.

Available Tools

1 tool
get_google_adsGet Google adsA
Read-onlyIdempotent

List the Google ads a company runs, read from Google's public Ads Transparency Center. Give a company domain (for example stripe.com) or an advertiser name, or lists of either. Returns one row per ad with the advertiser, ad ID, format (text, image, or video), first and last shown dates, a creative link, and the ad's Transparency Center page, plus one company summary row per input with Google's total ad count band, formats seen, and whether the company runs Google ads at all. Rows with no ads, blocked requests, or a changed Google page come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per ad row returned.

Inputs: region, domains, formats, max_ads, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (fetching Google Ads Transparency Center data) is unambiguous.

    Naming Consistency5/5

    The single tool follows a clear verb_noun pattern (get_google_ads). With only one name there is nothing to be inconsistent with.

    Tool Count3/5

    One tool is thin for a named 'server', though the domain (read-only ad lookup) is narrow enough that a single flexible tool handling domains, names, and lists is defensible. It sits at the borderline where more granular operations (e.g. per-format or per-advertiser queries) might be expected.

    Completeness4/5

    For a read-only transparency lookup, the surface covers the key needs: ad rows, per-company summaries, status rows for no-ads/blocked/changed pages, and error reporting with run IDs. Only minor gaps remain, such as no explicit filtering or historical-comparison operation.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers