Google Ads MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_ADS_AUTH_TYPE | Yes | Authentication type for Google Ads API | |
| GOOGLE_ADS_API_VERSION | No | API version override (default v19). Example: v21 | v19 |
| GOOGLE_ADS_CUSTOMER_ID | No | 10‑digit Ads customer ID. If omitted, tools will list accessible accounts and ask you to pick one | |
| GOOGLE_ADS_ACCESS_TOKEN | No | Direct token override for dev/tests (bypasses ADC) | |
| GOOGLE_ADS_GCLOUD_USE_CLI | No | Optional CLI token fallback (true/false) | |
| GOOGLE_ADS_DEVELOPER_TOKEN | Yes | Developer token (required for Ads API calls) | |
| GOOGLE_ADS_CREDENTIALS_PATH | No | Required for oauth and service_account modes - path to credentials file | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | No | Manager (MCC) account ID; only needed when acting on a child through an MCC |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_authB | Manage Google Ads auth: status; switch/refresh via gcloud; set_project/set_quota_project; optional oauth_login using env client id/secret to create ADC file. |
| execute_gaql_queryC | Execute GAQL. Optional: login_customer_id (aka MCC/manager account id) overrides env. |
| get_performanceC | Get performance (level: account|campaign|ad_group|ad). Optional: login_customer_id (aka MCC/manager account id) overrides env. |
| list_resourcesC | List GAQL FROM-able resources via google_ads_field (category=RESOURCE, selectable=true) or list accounts. output_format=table|json|csv. |
| gaql_helpB | Get GAQL help with local documentation and official Google Ads API links. Use topic for specific areas or search for keywords. |
| set_session_credentialsB | Establish a session with Google Ads credentials (multi-tenant mode only). |
| get_credential_statusC | Get credential status for a session (multi-tenant mode). |
| end_sessionC | End a session and clear credentials (multi-tenant mode). |
| refresh_access_tokenB | Refresh the access token for a session (multi-tenant mode). Requires GOOGLE_OAUTH_CLIENT_ID/SECRET. |
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 9 tools
Most tools have distinct purposes, such as execute_gaql_query for querying, get_performance for metrics, and manage_auth for authentication. However, there is some overlap between end_session, refresh_access_token, and set_session_credentials, all related to session management, which could cause minor confusion for an agent.
The tools generally follow a consistent verb_noun pattern, like execute_gaql_query and get_performance, with clear actions. A minor deviation is gaql_help, which uses a noun_verb format, but overall the naming is predictable and readable across the set.
With 9 tools, the count is well-scoped for a Google Ads API server, covering key operations like querying, performance analysis, resource listing, and authentication. Each tool serves a specific function without redundancy, making the set efficient and manageable.
The toolset provides strong coverage for core Google Ads workflows, including data querying, performance retrieval, and authentication management. A minor gap is the lack of tools for modifying resources, such as creating or updating campaigns, but agents can still perform essential read and analysis tasks effectively.