google-ads-function-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_ADS_MCP_HOST | No | Streamable HTTP bind host. | 127.0.0.1 |
| GOOGLE_ADS_MCP_PORT | No | Streamable HTTP bind port. | 8000 |
| GOOGLE_ADS_CLIENT_ID | Yes | OAuth client ID for Google Ads API. | |
| GOOGLE_ADS_API_VERSION | No | Optional Google Ads API version; when omitted, the gateway uses the highest version packaged by google-ads-python. | |
| GOOGLE_ADS_CLIENT_SECRET | Yes | OAuth client secret for Google Ads API. | |
| GOOGLE_ADS_REFRESH_TOKEN | Yes | OAuth refresh token for Google Ads API. | |
| GOOGLE_ADS_MCP_AUTH_TOKEN | No | Optional bearer token required for Streamable HTTP MCP requests. | |
| GOOGLE_ADS_RETRY_ATTEMPTS | No | Number of retry attempts for API calls. | 3 |
| GOOGLE_ADS_RUN_LIVE_TESTS | No | Set to '1' only when intentionally running live read-only tests. | 0 |
| GOOGLE_ADS_DEVELOPER_TOKEN | Yes | Your Google Ads API developer token. | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | Yes | Manager/MCC account ID used as the discovery root. | |
| GOOGLE_ADS_ALLOWED_CUSTOMER_IDS | Yes | Comma-separated list of customer IDs explicitly authorized for reporting. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | Discover accessible Google Ads accounts using the configured MCC context. |
| get_account_detailsA | Return details for one explicitly allow-listed Google Ads customer. |
| list_campaignsA | List campaigns for one explicitly allow-listed Google Ads customer. |
| get_campaign_detailsB | Return details for one campaign in an explicitly allow-listed customer. |
| get_campaign_costA | Return daily campaign cost rows for an explicitly allow-listed customer. |
| get_campaign_performanceC | Return campaign performance rows for one or more explicitly allow-listed customers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tools are mostly distinct: list vs details pairs for accounts and campaigns are clear, and cost vs performance have separate purposes. There is minor potential confusion between get_campaign_cost and get_campaign_performance since cost could be considered part of performance, but the descriptions clarify the difference.
All tool names follow a consistent verb_noun pattern with snake_case, such as list_accounts, get_account_details, and list_campaigns. The naming is predictable and makes the tool's purpose clear.
Six tools is a well-scoped set for a Google Ads read-only gateway. Each tool covers a meaningful access or reporting need without unnecessary redundancy.
The tool surface covers core account discovery, campaign listing, details, cost, and performance reporting. It lacks deeper campaign management or ad-level reporting, but for a read-only function gateway the major workflows are covered.