Skip to main content
Glama

Proxy

by dev.useproxy
OverviewDiscussionsAdmin

Get Google Ads Transparency Center Ads

get_google_ads
Read-only

Use this to retrieve all active ads from a brand on Google — Search, Display, YouTube, and other networks. Requires advertiser ID or domain from get_google_platform_id. Returns creatives with dates and URLs for competitive analysis. SHOWING THE ADS — once you have the creative details, you MUST call show_ad_carousel at least once this turn so the user SEES the ads as visual proof, not only reads about them. Pass each Google ad as {ad_url} copied from this tool's output (the server fills in the creative, copy and media from cache). Interleave carousels WITH your analysis — one per point you make, each showing the ads that evidence THAT point. Structure strictly as point → its carousel → next point → its carousel; NEVER stack carousels back-to-back or dump all points as a list after the carousels. Be generous: across your carousels, show MOST of the ads this tool returned (up to 20 per carousel) — skip only irrelevant or near-duplicate ads; never render just 2-3 when a dozen were found. If discussed points don't cover all the ads, close with a broader carousel of the rest. You may mix Meta {ad_id, page_id}, Google {ad_url}, LinkedIn {linkedin_id}, and TikTok {tiktok_id} refs in a single carousel when a point spans platforms. Skip it only when there were zero ads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax ads to return (default 100, max 1000), fetched in pages at 1 credit each.
topicNoFilter by topic; "political" requires region.
domainNoCompany domain, e.g. "nike.com". Suits company-wide search; one of domain or advertiser_id is required.
regionNoRegion code, required when topic is "political", e.g. "US".
contextNoOne plain sentence, 8-20 words, starting with a verb, stating what the user is trying to accomplish in this conversation. Name the brand, competitor, industry, or topic involved. Reuse the exact same sentence on every tool call in this conversation. Never include people's names, emails, phone numbers, credentials, or internal company details. Never describe this tool or why it was chosen. Example: 'Compare Notion and Coda Meta ads to find hooks for a productivity app launch.'
advertiser_idNoAdvertiser ID from get_google_platform_id, e.g. "AR01614014350098432001". Targets one regional entity.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / advertiser_id / description
      Added value: +"Advertiser ID from get_google_platform_id, e.g. \"AR01614014350098432001\". Targets one regional entity."
    • addedInput schema / properties / domain / description
      Added value: +"Company domain, e.g. \"nike.com\". Suits company-wide search; one of domain or advertiser_id is required."
    • addedInput schema / properties / limit / description
      Added value: +"Max ads to return (default 100, max 1000), fetched in pages at 1 credit each."
    • addedInput schema / properties / region / description
      Added value: +"Region code, required when topic is \"political\", e.g. \"US\"."
    • addedInput schema / properties / topic / description
      Added value: +"Filter by topic; \"political\" requires region."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the burden is lower. The description still adds valuable behavior: the returned payload is creatives with dates and URLs, the ID/domain prerequisite, and the mandatory downstream show_ad_carousel step, which is a genuine workflow constraint an agent must respect.

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

Conciseness3/5

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

The purpose is correctly front-loaded, but the entire 'SHOWING THE ADS' block is a long procedural prescription about interleaving carousels that arguably belongs in the carousel tool or workflow prompt. It is not pure noise, but it dominates the definition and buries the retrieval purpose under presentation rules.

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?

An output schema exists, so return-value documentation is unnecessary, and annotations cover safety. The description still supplies the prerequisite source, the content of the results, and the follow-up workflow, leaving little an agent needs missing before calling it.

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 all seven parameters are already documented in the schema, including the limit/pagination, topic, region, domain and advertiser_id semantics. The description adds only the sourcing of advertiser_id/domain from get_google_platform_id, which the schema does not state, but otherwise does not go beyond the structured fields. Baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource — 'retrieve all active ads from a brand on Google — Search, Display, YouTube, and other networks' — and the title pins it to the Google Ads Transparency Center, which cleanly separates it from get_meta_ads or the LinkedIn/TikTok siblings. It does not explicitly contrast against get_google_ad_details, so the differentiation is implied rather than stated.

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?

It names a prerequisite ('advertiser ID or domain from get_google_platform_id') and a purpose ('for competitive analysis'), which is real context. However, it offers no explicit when-not guidance and never contrasts this tool with the adjacent get_google_ad_details or get_google_platform_id siblings, leaving the agent to infer the routing.

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

All Proxy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources