Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Google Ads Transparency Scraper

scrape_google_ads_transparency

Retrieve a brand's Google Ads Transparency Center ads by domain or advertiser name, including shown dates, formats, Search ad copy, and YouTube links; also check which domains run Google ads.

Instructions

Scrape a brand's ads from the Google Ads Transparency Center by domain or advertiser name: first/last shown dates, format, Search ad copy as text (headline, description, sitelinks) and YouTube links. 'domainCheck' mode tells you which domains run Google ads. Priced per ad. Runs the Apify actor zrk1212/google-ads-transparency-ad-copy on your Apify account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrape_google_ads_transparency"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoGet ads (default) or just check whether domains advertise.
regionNoCountry code (default US) or 'anywhere'.
domainsNoAdvertiser domains, e.g. ['nike.com'].
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
extraInputNoAny other input field of the Apify actor zrk1212/google-ads-transparency-ad-copy, passed through as-is. See https://apify.com/zrk1212/google-ads-transparency-ad-copy/input-schema
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
advertiserNamesNoAdvertiser names to look up.
maxAdsPerTargetNoAds per domain or advertiser (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorld=true, readOnly=false, destructive=false, idempotent=false, so the safety/mutation profile is covered. The description adds genuinely new behavior: 'Priced per ad' discloses the cost model, and 'Runs the Apify actor zrk1212/... on your Apify account' discloses the account/credential dependency and the underlying actor identity. It stops short of describing run duration, failure/empty-result behavior, or how partial runs are resumed (though the schema covers waitSecs).

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?

Three sentences, front-loaded with the capability and the returned data, then the mode distinction, then operational notes (pricing, actor, account). No filler, though the first sentence is a long clause stack that could be split for faster scanning.

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

Completeness4/5

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

For a 9-parameter, nested-extraInput scraper with no output schema, the description covers what comes back (dates, format, ad text, sitelinks, YouTube links), both targeting paths, the two modes, and the cost/account model. Remaining gaps are async/pagination mechanics and the passthrough nature of extraInput, which the schema already documents.

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 is already documented, and the description correctly stays out of the way. It adds only marginal semantic value beyond the schema by clarifying that domainCheck answers a yes/no advertising question while the default mode returns ad copy, and by framing inputs as 'domain or advertiser name'. Baseline 3 is appropriate.

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 ('Scrape a brand's ads from the Google Ads Transparency Center') plus the two lookup keys (domain or advertiser name) and enumerates the returned fields (dates, format, ad copy, YouTube links). The 'domainCheck' mode is called out as a distinct capability, so an agent can tell what it gets without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: the description explains that 'domainCheck' tells you which domains run Google ads, which hints at when that mode applies, and it notes 'by domain or advertiser name' as the two entry paths. There is no explicit when-to-use/when-not-to-use guidance, no prerequisite statement (e.g. at least one of domains/advertiserNames must be supplied), and no routing to alternatives such as get_run_results for long runs.

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