flin-google-keyword-planner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_ADS_CLIENT_ID | Yes | Your OAuth 2.0 client ID. | |
| GOOGLE_ADS_CUSTOMER_ID | No | Default customer ID to use if no customer_id argument is passed. | |
| GOOGLE_ADS_CLIENT_SECRET | Yes | Your OAuth 2.0 client secret. | |
| GOOGLE_ADS_REFRESH_TOKEN | Yes | Your OAuth 2.0 refresh token. | |
| GOOGLE_ADS_USE_PROTO_PLUS | No | Whether to use proto-plus message format (true by default). | true |
| GOOGLE_ADS_DEVELOPER_TOKEN | Yes | Your Google Ads API developer token. | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | No | Login customer ID for MCC accounts. |
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 |
|---|---|
| google_ads_authorization_urlC | Create the Google OAuth consent URL for generating a Google Ads refresh token. |
| google_ads_exchange_authorization_codeC | Exchange a Google OAuth authorization code for a session refresh token. |
| google_ads_start_local_oauth_flowC | Start a local OAuth callback server and return the Google consent URL. |
| google_ads_oauth_statusA | Return local OAuth callback status and whether a runtime token is available. |
| keyword_ideas_from_keywordsC | Generate keyword ideas using KeywordSeed. |
| keyword_ideas_from_urlC | Generate keyword ideas using UrlSeed. |
| keyword_ideas_from_keyword_and_urlC | Generate keyword ideas using KeywordAndUrlSeed. |
| keyword_ideas_from_siteC | Generate keyword ideas using SiteSeed. |
| keyword_ideas_historicalC | Generate keyword ideas with historical metrics options (year-month range). |
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
Each tool has a clearly distinct purpose: OAuth flow tools handle different stages (authorization URL, code exchange, status, local server), and keyword tools use distinct seed types (keyword+URL, keywords, site, URL, historical). No ambiguity between any pair.
All tools follow a consistent snake_case pattern. OAuth tools use the prefix 'google_ads_' followed by a verb_noun describing the action (e.g., authorization_url, exchange_authorization_code). Keyword tools uniformly start with 'keyword_ideas_from_' and specify the seed type. This consistent structure helps agents predict naming.
9 tools is well-scoped for a Google Ads Keyword Planner MCP. It covers authentication setup (4 tools) and keyword idea generation from multiple seed types (5 tools), without unnecessary duplication. The count feels appropriate for the domain.
The tool set covers the full OAuth lifecycle (authorization, exchange, status, local flow) and provides all common ways to generate keyword ideas: from keywords, URL, site, and historical data. There are no obvious gaps for the stated purpose of keyword planning.