Skip to main content
Glama
Google Ads Transparency MCP

Google Ads Transparency MCP

Google Ads Transparency Scraper: Competitor Ads

publicrecords--google-ads-transparency-scraper
Read-only

Track competitors' Google ads by domain, advertiser ID, or name: retrieve new, running, and stopped ads with dates, days shown, and links for a chosen country.

Instructions

Google Ads Transparency Scraper: Competitor Ads. Track competitors' Google ads by website or advertiser ID: new, running and stopped ads with first and last shown dates, days shown and ad links. No login, no proxy.

When to use: Use when you need the Google ads a competitor runs (by website domain, Google advertiser ID, Ads Transparency Center link or advertiser name): which ads are new, still running or stopped in a look-back window, with first and last shown dates, days shown and ad links, optionally for one country. Good for weekly competitor ad monitoring; not for ad spend, clicks or keyword bids.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "publicrecords/google-ads-transparency-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/google-ads-transparency-scraper

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "targets": "<targets>"
    },
    "name": "publicrecords--google-ads-transparency-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOnly ads shown in this country. "Anywhere" returns ads from every country.anywhere
targetsYesOne per line: a website domain (nike.com), a Google advertiser ID (AR…), an Ads Transparency Center link, or an exact advertiser name. Example: ["nike.com"]
statusesNoLeave all selected for every ad Google still lists (about one year back). Select only new, running and stopped for a faster weekly monitor.
sinceDaysNoAds first shown in this window are "new"; ads that stopped inside it are "stopped". Google lists an ad 2–3 days after it runs, so on a schedule use your interval plus 3 days (10 for weekly) and match repeats by adId.
maxAdsPerTargetNo0 means no limit. A website search returns every ad that links to it, which for big marketplaces is millions; use an advertiser ID for one company's own ads.
includeRegionStatsNoAdds the countries each ad ran in and, for EU countries, Google's impression ranges. Slower: one extra request per ad.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive, and the description corroborates and extends them: it discloses that each call starts a new Apify Actor run under the caller's own APIFY_TOKEN and Apify account, explains the run/dataset IDs used for paging, and notes no login or proxy is needed. That account-usage and run-creation disclosure is exactly the kind of cost/auth behavior annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The labeled sections (When to use / Returns / Behavior / Docs) are well front-loaded and easy to scan. There is mild redundancy — 'first and last shown dates, days shown and ad links' appears twice, and the ad-status list is restated — but nothing is padded enough to obscure the key facts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by explaining the return shape (one row per result as structured JSON) and how to page the full dataset via run and dataset IDs. Combined with auth, cost-account, and exclusion information, an agent has everything needed to call this correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter already carries meaning in the schema, including the look-back window and the 0-means-no-limit convention. The description only loosely echoes those points ('optionally for one country', target input forms) and adds no new syntax or constraint beyond what the schema states, so this is a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (track competitors' Google ads by website or advertiser ID) and enumerates the outputs (new/running/stopped ads, first/last shown dates, days shown, ad links). It also explicitly distinguishes itself from adjacent concerns by saying it is 'not for ad spend, clicks or keyword bids,' so the agent knows exactly what class of tool this is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'When to use' block names the accepted input forms (domain, advertiser ID, Transparency Center link, advertiser name), the monitoring scenario (weekly competitor ad monitoring), and an explicit exclusion (spend/click/keyword-bid data). The schema-level advice about using an advertiser ID for big marketplaces and adding 3 days to a scheduling interval is real operational guidance rather than restatement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.