Skip to main content
Glama

google_ads_transparency

Search and retrieve Google Ads Transparency Center data by advertiser ID or keyword, filtered by platform, region, date range, and creative format.

Instructions

Pulls ad data from the Google Ads Transparency Center, looked up by advertiser ID or keyword/domain, filterable by platform, region, date range, and creative format. Costs 5 API credits per request. [Credits: 5 API credits per request] Notes: Provide either advertiser_id or text (not necessarily both). political_ads=true requires region to be set. Pagination via next_page_token found in scrapingdog_pagination of the response. Note the endpoint path uses a slash (google/ads_transparency) rather than an underscore, unlike other endpoints in this category. Returns: { search_information: {total_results}, ad_creatives: [{advertiser_id, advertiser, ad_creative_id, format, link, total_days_shown, first_shown, last_shown}], scrapingdog_pagination: {next_page_token} }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoMaximum number of ad results to return per request. (default: 40)
htmlNoSet true to receive raw HTML of the page instead of parsed JSON. (default: false)
textNoKeyword or domain to search within the Google Ads Transparency Center, equivalent to typing into its search bar. Alternative to advertiser_id; when provided, advertiser_id is not required.
regionNoNumeric region code to limit results to a geographic region, e.g. 2840 for the United States. Omit for global results.
end_dateNoLatest date for returned ads, format YYYYMMDD, e.g. 20221231. To fetch a single day, set end_date to one day after start_date.
platformNoFilter results to a specific platform. Allowed values: PLAY (Google Play), MAPS (Google Maps), SEARCH (Google Search), SHOPPING (Google Shopping), YOUTUBE (YouTube). Leave blank for all platforms.
start_dateNoEarliest date for returned ads, format YYYYMMDD, e.g. 20221201.
advertiser_idNoUnique ID assigned to a Google advertiser, found in the Ads Transparency Center URL (e.g. AR17828074650563772417 from https://adstransparency.google.com/advertiser/AR17828074650563772417). Accepts a single ID or comma-separated list. Alternative to `text`.
political_adsNoSet true to include only political advertisements (tracked/excluded from regular results by default). Must be combined with `region`. (default: false)
creative_formatNoFilter ads by creative type. Allowed values: text, image, video.
next_page_tokenNoToken for fetching the next page of results, obtained from the previous response's scrapingdog_pagination.next_page_token.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses API credit cost (5 per request), pagination mechanism, endpoint path quirk, and return structure. While it omits auth or rate limits, it covers key behavioral aspects well.

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

Conciseness5/5

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

Description is efficiently structured: front-loaded purpose, followed by usage notes, pagination, endpoint correction, and return schema. Every sentence adds value without redundancy.

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?

Given 11 parameters, no annotations, and no output schema, the description is remarkably complete. It explains alternative parameter groups, pagination, cost, and return format. Users have enough to use tool correctly without external docs.

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

Parameters4/5

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

Schema coverage is 100% (all params described). The description adds value beyond schema by explaining usage relationships (advertiser_id vs text, political_ads+region), pagination token origin, and endpoint path note, raising it above 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?

The description clearly states it pulls ad data from Google Ads Transparency Center, specifying lookup methods (advertiser ID or keyword/domain) and multiple filters. It distinguishes itself from sibling Google scraping tools by focusing on ad transparency, making purpose unambiguous.

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

Usage Guidelines4/5

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

The description gives explicit usage conditions: provide either advertiser_id or text, political_ads requires region, pagination via next_page_token. It lacks explicit comparison to siblings, but given no direct competition, this is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server