Skip to main content
Glama

Read Google Ads data

google_ads_read
Read-onlyIdempotent

Reads Google Ads accounts. action "list_tools" lists every Google Ads operation with its field names and flags (get_tool_schema returns the input schema); it does not call Google and is free. action "execute" runs one read: {"action":"execute","tool_name":"google_account_summary","arguments":{}}. Reads:

  • google_account_summary: The connected Google Ads account: name, currency, time zone, status, test or production, manager or client.

  • google_list_campaigns: Campaigns in the Google Ads account: status, why they do or do not serve, type, bidding, budget and dates. Removed campaigns only on request.

  • google_list_ad_groups: Ad groups of one Google Ads campaign: status, type and the default CPC bid.

  • google_ad_performance: Google Ads metrics per ad over a period: cost, clicks, CTR, CPC, conversions, CPA, ROAS, with ad strength and serving status.

  • google_search_terms: What people actually searched for when your Search ads showed, with the keyword that matched and the metrics of each search term.

  • google_placement_performance: Where Display, Video, Demand Gen and Performance Max ads were shown — websites, apps, YouTube channels and videos — with metrics.

  • google_reach_frequency: How many unique people Display, Video and Demand Gen campaigns reached and how often each saw the ads, over a period.

  • google_conversion_performance: Conversions and their value per conversion action over a period, for the account or split by campaign.

  • google_recommendations: Recommendations Google Ads itself offers for the account, grouped by type, with Google's own estimate of what applying them would change, plus the budget options and keyword ideas behind them. Read only: this server never applies a recommendation.

  • google_landing_pages: Landing pages of Google Ads over a period: spend, clicks, conversions and value per page, with the mobile loading speed score Google gives the page, and findings about pages that take money without converting.

  • google_campaign_structure: What a Google Ads campaign is made of: its ad groups with bids, and on request their keywords, negative keywords and ads.

  • google_campaign_settings: All settings of one Google Ads campaign: dates, bidding and targets, budget, networks, location options, tracking template and URL parameters, frequency caps, Shopping feed and AI Max.

  • google_ad_group_settings: Settings of one Google Ads ad group: status, type, bids and targets, ad rotation, targeting or observation per audience dimension, tracking, device bid adjustments and Demand Gen channels.

  • google_ads: Ads with their texts: headlines, descriptions, paths and final URLs of responsive search, display and Demand Gen ads.

  • google_ad_policy_issues: Ads that Google disapproved or limited, with the policy topics and the evidence Google gives.

  • google_labels: Labels of the Google Ads account, or the labels on one campaign.

  • google_change_history: Who changed what in the Google Ads account and when: campaigns, budgets, ad groups, ads, keywords, targeting and assets.

  • google_campaign_targeting: Who and where a Google Ads campaign targets: locations and radius, languages, ad schedule, devices, audiences, demographics and exclusions.

  • google_ad_group_criteria: Targeting inside ad groups: keywords, placements, YouTube channels and videos, apps, topics, audiences and demographics — for Search, Display and Demand Gen.

  • google_search_audiences: Find audiences by name: Google interest and in-market categories, the account custom audiences, remarketing lists and audiences.

  • google_locations: Find Google location ids by name — countries, regions, cities, postal codes — with their full names and parents.

  • google_languages: Languages Google Ads can target, with their ids and codes; search narrows by name or code.

  • google_campaign_assets: Assets (extensions) a campaign uses — sitelinks, callouts, structured snippets, calls, images, texts — at campaign, account and ad group level.

  • google_asset_library: Assets already in the account library — images, YouTube videos, texts, sitelinks, callouts and more — to reuse in campaigns.

  • google_pmax_asset_groups: Asset groups of a Performance Max campaign: status, why they serve or not, ad strength, final URLs and metrics over a period.

  • google_pmax_assets: Texts, images, logos and videos in Performance Max asset groups, with whether each serves and why not.

  • google_pmax_signals: Search themes and audience signals of Performance Max asset groups — the hints that steer who Performance Max looks for.

  • google_conversion_goals: Which conversion goals a campaign bids for: each goal category and source, and whether it is biddable.

  • google_product_groups: The product group tree of a Shopping ad group: how products are split by brand, category, type, item id or custom label, with bids.

  • google_listing_filters: Which products or pages a Performance Max asset group advertises: its listing group filter tree.

  • google_merchant_center_links: Merchant Center accounts linked to this Google Ads account — the product feeds Shopping and Performance Max can use.

  • google_conversion_actions: Conversion actions of the account: what counts as a conversion, primary or secondary, value, counting, attribution and windows.

  • google_wasted_spend: Where Google Ads money brings nothing back: campaigns with no conversions or with a cost per conversion far above target, and the costliest search terms that never converted.

  • google_budget_allocation: A plan to move daily budget between Google Ads campaigns toward those that bring conversions (or value) cheaper, within limits. Nothing is changed.

  • google_explain_change: Why a Google Ads metric changed between two periods: which campaigns moved it, and which edits in the account (budgets, statuses, bids, targeting, ads) happened around that time.

  • google_ad_copy_brief: Everything needed to write new Google ad texts for a campaign: current headlines and descriptions with Google ratings, converting keywords and search terms, landing pages and character limits. The assistant writes the texts.

  • google_search_term_insights: What to do with search terms: converting terms that are not keywords yet, costly terms that never converted (negative keyword candidates), and how each match type performs.

  • google_revenue_report: Money your CRM or payment system received beside Google Ads spend, per campaign or ad group: revenue, payments, ROAS, cost per payment and a verdict. Payments that matched nothing are a line of their own.

  • google_audit_conversion_tracking: Audit how this Google Ads account tracks conversions: a 0–100 score and A–F grade with the findings behind it.

  • google_diagnose_funnel: Walk the Google Ads funnel step by step — tracking, value, traffic, conversion, landing pages, spend — and stop at the first broken step.

  • google_list_signals: What the watchdog found in this Google Ads account and has not seen resolved.

  • google_run_watch_now: Run the watchdog over this Google Ads account right now instead of waiting for its next pass.

  • google_get_signal_briefing: One finding of the watchdog or a monitor on this Google Ads account, with the live context to judge it: status, daily numbers, recent changes.

  • google_list_monitors: Monitors of this Google Ads account: their conditions, status, last check and how often they triggered.

  • google_get_monitor_history: When a Google Ads monitor triggered, on which campaigns or ad groups, with what numbers, and whether an email went out.

  • google_test_monitor: Dry-run a Google Ads monitor now: which campaigns or ad groups would trigger and which are skipped, without recording or emailing. google_campaign_performance is its own tool, not behind this router. Read-only and free: changes nothing and does not count toward the monthly change limit. Google counts every request toward this server’s daily Google Ads API quota, so a read can be refused for a while when that quota runs low.

Input Schema

NameRequiredDescriptionDefault
actionYeslist_tools: every operation with its field names, flags and router. execute: run the read named by tool_name.
argumentsNoFor execute: the fields of the operation, plus "connection" when several ad accounts are connected. Omit or {} when it has none.
tool_nameNoFor execute: the operation name from list_tools, e.g. google_list_campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds meaningful operational context: list_tools is free and does not call Google, execute reads count against the daily Google Ads API quota, and reads can be refused when quota runs low. It also states the server never applies recommendations and changes nothing.

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 opening action semantics are front-loaded and clear, but the enormous operation catalog makes the description far longer than necessary. Much of that catalog duplicates what the list_tools action already provides, though the structure remains readable.

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?

For a router tool with many underlying reads, it explains the discovery path (list_tools, get_tool_schema), the execution path (execute with tool_name and arguments), the read-only/free behavior, and the API quota constraint. No output schema exists, but the return-shape burden is appropriately delegated to the discovery actions.

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 description coverage is 100%, so the baseline is 3, but the description adds substantial meaning beyond the schema by enumerating all valid tool_name values and describing what each read returns. It does not detail every operation's arguments, leaving that to list_tools/get_tool_schema.

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?

Starts with a specific verb and resource: reads Google Ads accounts. It clearly separates the two actions, list_tools versus execute, and explicitly says google_campaign_performance is not behind this router, which distinguishes it from a key sibling.

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?

Explains when to use list_tools (free, no Google call, lists operations) versus execute (runs one named read), and provides a concrete execute example. It also names the main sibling alternative by stating google_campaign_performance is its own tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.