Google Ads MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_accessible_customersA | List Google Ads customer ids the authenticated user can access. |
| searchA | Run a GAQL query against one account and return the matching rows. Args: customer_id: Account id (dashes are stripped automatically). gaql: A Google Ads Query Language statement containing a SELECT clause. page_size: Max rows to return (default 1000). login_customer_id: Optional manager/login id for accounts not under the manager in google-ads.yaml. For a direct-access account, pass its own id here. |
| describe_resourceA | Discover selectable/filterable fields of a resource to help build GAQL. Args: resource: A resource/metric/segment prefix, e.g. 'campaign', 'ad_group', 'metrics', 'segments'. |
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 3 tools
Each tool has a distinct purpose: listing accessible customers, running GAQL queries, and describing resource fields. No overlap in functionality.
All tool names follow a consistent verb_noun pattern: list_accessible_customers, search, describe_resource. Clear and predictable.
Three tools is on the lower end but still within the reasonable range for a focused query interface. The count is appropriate for the server's stated purpose.
The tools cover listing accounts and querying data, but lack create, update, or delete operations for Google Ads resources. This is a notable gap for a full API surface.