AdsAgent — Google Ads MCP

google_ads_keyword_ideas_generate

Read-only

Generate bounded Google Search keyword ideas with historical metrics for one owned customer. Read-only and hot-cached.

Input Schema

Name	Required	Description	Default
`url`	No
`limit`	No
`network`	No		GOOGLE_SEARCH
`keywords`	No
`language`	No	Language name, for example English.
`customer_id`	Yes	10-digit Google Ads customer id.
`language_id`	No	Legacy Google language_constant; prefer language by name. The default is English.	1000
`geo_target_ids`	No
`connection_context`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`meta`	No
`error`	No
`ideas`	No
`needs`	No
`reason`	No
`retryable`	No
`error_code`	No
`customer_id`	No
`next_action`	No
`support_ref`	No
`invalid_fields`	No
`rejected_paths`	No
`origin_support_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "customer_id": {
+      "type": "string"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "code": {
+                  "type": "string"
+                },
+                "details": {
+                  "additionalProperties": true,
+                  "properties": {},
+                  "type": "object"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "retryable": {
+                  "type": "boolean"
+                },
+                "support_ref": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "ideas": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "invalid_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": true,
+      "properties": {
+        "complete": {
+          "type": "boolean"
+        },
+        "has_more": {
+          "type": "boolean"
+        },
+        "limit": {
+          "type": "integer"
+        },
+        "next_continuation": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "next_cursor": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "pagination_complete": {
+          "type": "boolean"
+        },
+        "returned_count": {
+          "type": "integer"
+        },
+        "source": {
+          "type": "string"
+        },
+        "total_count": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "truncated": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "needs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_action": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {},
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "origin_support_ref": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "rejected_paths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "support_ref": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / language / description

Previous value: -"Language name, for example 英语."New value: +"Language name, for example English."

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Language name, for example 英语.",
+  "type": "string"
+}

addedInput schema / properties / language_id / description

Added value: +"Legacy Google language_constant; prefer language by name. The default is English."

removedInput schema / properties / language_id / maxLength
```
Removed value: -20
```

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
First observedSep 16, 2026

TDQS

B3.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so 'Read-only' is redundant repetition. 'Hot-cached' is genuine added value — it tells the agent repeated calls may return served/cached results without a live Google round-trip — and 'bounded' hints at a capped result set. Missing are the connection_context/auth requirement and any note on cost or latency of a cache miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence, front-loaded with the action and resource, with no filler. It is arguably too terse for a 9-parameter tool, but nothing in the text is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters, 33% schema coverage and no parameter guidance in the description, an agent cannot tell how the seed inputs (keywords vs url) behave or what network/geo/language defaults imply. An output schema exists so return values need not be explained, but the input-side story and the connection_context requirement are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (customer_id and language_id are documented in-schema), while url, limit, network, keywords, geo_target_ids and connection_context are undocumented. The description only gestures at customer scoping ('one owned customer') and does not explain that url and keywords are alternative seed inputs, nor how geo/language targeting interacts with the results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a concrete verb and resource ('Generate ... Google Search keyword ideas') plus meaningful scope ('bounded', 'with historical metrics', 'for one owned customer'). It is clear enough to separate this from siblings like google_ads_keyword_themes or google_ads_keyword_forecast_metrics, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'keyword ideas' and 'for one owned customer' suggest an ideation/expansion step against an existing account. There is no statement of when to prefer this over google_ads_keyword_themes (thematic ideation) or google_ads_keyword_forecast_metrics (projected performance), and no stated prerequisites beyond the customer being owned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdsAgent — Google Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?