compare_periods
Compare performance between two date ranges.
LABSCO SUMMARY
Multi-account routing as a first-class idea, not a restart.
For anyone running ads across several accounts, the account manager is the whole point: every tool takes an account name, there is a default you can change mid-session, and the credentials for each live in one config file. The reporting itself goes down to the level that answers questions — quality scores on keywords, and the search terms that actually triggered the ads, rather than only campaign totals.
What it is
A read-oriented Google Ads reporting server built around an account manager, so one running server can address many client or in-house accounts by name.
What you get
- The configured accounts listed with which one is currently the default, and the default switched without restarting
- Accessible customer accounts listed, or the child accounts under a manager account when you name one
- Top-level spend and conversion totals for an account over a date range
- Two date ranges compared, with an optional breakdown, for period-over-period reporting
- Campaigns listed with a status filter, and campaign performance metrics over a range
- Keyword-level performance including quality scores, bounded by a row limit
- The actual search terms that triggered your ads
- Ad-level performance — headlines, descriptions, click-through rate, conversions
Requirements
A Google Ads API developer token from the API Center, passed as GOOGLE_ADS_DEVELOPER_TOKEN, plus an accounts file: GOOGLE_ADS_ACCOUNTS_CONFIG points at an accounts.json holding the OAuth credentials for each account you want reachable, and the repository ships an accounts.example.json documenting its shape. Run it with uvx mcp-google-ads-multi over stdio, from the PyPI package mcp-google-ads-multi, currently 0.1.0; MCP_TRANSPORT=sse with MCP_HOST and MCP_PORT switches to remote hosting. Transient Google Ads API failures are retried with backoff. The project describes its release posture as beta.
Setup effort
One command plus credentials — uvx mcp-google-ads-multi, then supply credentials
USE CASES
01
Reporting on a client account you have not touched this week
List the configured accounts, switch the default to that client, then read the spend and conversion totals.
02
Showing whether this month beat last month
Compare the two date ranges directly, with a breakdown if you need to see where the change came from.
03
Finding which campaigns are carrying the spend
List the campaigns, then pull their performance across the range.
04
Working out what people actually searched for
Read the search terms report for the campaign, then look at the keywords and their quality scores.
05
Deciding which creative to keep
Pull ad-level performance with the headlines and descriptions alongside the click-through and conversion numbers.
06
Mapping what an account login can even reach
List the accessible customers, and the child accounts under a manager account.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_account_summary
Get top-level spend and conversion totals for an account.
get_ad_performance
Get ad-level performance (headlines, descriptions, CTR, conversions).
get_campaign_performance
Get campaign performance metrics for a date range.
get_keyword_performance
Get keyword-level performance including quality scores.
list_accounts
List all configured Google Ads accounts and which is the current default.
list_campaigns
List campaigns for an account.
list_customers
List all accessible Google Ads customer accounts.
If customer_id is provided, lists child accounts under that MCC. Otherwise lists all accessible accounts for this login.
search_terms_report
Get actual search terms that triggered your ads.
set_default_account
Set the default account used when no account is specified in other tools.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. Nine of the ten only read; set_default_account changes which account later calls address. Nothing edits campaigns, budgets, bids or creatives.
Requires
- uvx on PATH
- GOOGLE_ADS_DEVELOPER_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-google-ads-multiMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"google-ads": {
"command": "uvx",
"args": [
"mcp-google-ads-multi"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_ADS_ACCOUNTS_CONFIG": "/Users/<YOUR_USERNAME>/.config/mcp-google-ads/accounts.json"
}
}
}
}
