MCP Marketing Analytics
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_ADS_CLIENT_ID | No | Google Ads OAuth client ID | |
| GOOGLE_ADS_CUSTOMER_ID | No | Google Ads customer ID | |
| GOOGLE_ADS_CLIENT_SECRET | No | Google Ads OAuth client secret | |
| GOOGLE_ADS_REFRESH_TOKEN | No | Google Ads OAuth refresh token | |
| GOOGLE_ADS_DEVELOPER_TOKEN | No | Google Ads developer token | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | No | Google Ads login customer ID |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| data_source_discoveryA | List available marketing data sources and their configuration requirements |
| accounts_discoveryA | List connected marketing accounts for the selected data source |
| field_discoveryB | List available fields for a given marketing data source |
| data_queryB | Execute a marketing analytics query using the selected source, accounts, fields, and date range |
| get_query_resultsA | Retrieve the result of a previously executed query by schedule ID |
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 5 tools
Each tool targets a distinct step in the analytics workflow: source discovery, account discovery, field discovery, query execution, and result retrieval. There is no overlap between these purposes, so an agent can confidently select the right tool.
The first three tools follow a consistent 'X_discovery' pattern, but the last two deviate with 'data_query' and 'get_query_results', mixing structural conventions. While all names use snake_case, the inconsistency in pattern makes the naming less predictable.
With only five tools, the set is well-scoped for a focused marketing analytics server. Each tool serves a necessary function in the pipeline without redundancy or bloat.
The tool set covers the full discovery-to-results lifecycle: discover sources, accounts, fields, execute a query, and retrieve results. There are no obvious gaps for read-only analytics operations.