Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Keyword ideas

discover_keywords

Read-only

Generate keyword ideas from seed terms or a website URL, with options for monthly search volumes and geotargeting. Get competition and bid estimates to inform your Google Ads strategy.

Instructions

Discover new keyword ideas using Google Ads Keyword Planner.

Mirrors the "Discover new keywords" UI in Keyword Planner:

Start with keywords: pass seed_keywords (e.g. ["running shoes"])
Start with a website: pass url (e.g. "https://example.com/products")

Set include_monthly_volumes=true for per-month search history (last 24 months, top-20 ideas) plus a seasonality insight — use when the user asks about demand trends, seasonality, or "when should I ramp budget".

Both together: keywords + url for more targeted ideas

Returns keyword ideas sorted by avg monthly search volume, with competition level (LOW/MEDIUM/HIGH) and top-of-page bid range.

geo_target_id: geo target constant (2276=Germany, 2840=USA, 2826=UK) language_id: language constant (1000=English, 1001=German, 1002=French) page_size: max keyword ideas to return (default 50, max 1000)

Input Schema

TableJSON Schema

Name	Required	Default
`url`	No
`page_size`	No
`customer_id`	No
`language_id`	No	1000
`geo_target_id`	No	2276
`seed_keywords`	No
`include_monthly_volumes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.2Sep 7, 2026
Removedv0.13.0Jul 22, 2026
Changed1 schema field changedv0.12.0Jul 12, 2026
- addedInput schema / properties / include_monthly_volumes
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv0.9.0Jun 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnlyHint annotation already indicates the operation is read-only, and the description adds transparency by summarizing the output (keyword ideas sorted by avg monthly search volume, competition, bid range). It does not introduce any contradiction with the annotation.

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?

The description is well-structured with bullets for input modes and a separate paragraph for include_monthly_volumes, followed by output details and parameter hints. It is somewhat repetitive but remains concise and easy to scan.

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

Completeness4/5

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

It provides enough context for an agent to understand the tool's purpose, when to use the optional flag, and what to expect in response. It lacks an explicit statement about the output schema, but that is not required given that the output format is described in prose.

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

Parameters4/5

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

The description explains the purpose of seed_keywords, url, include_monthly_volumes, geo_target_id, language_id, and page_size with examples. It does not describe customer_id, which is a gap given that the schema itself has no parameter descriptions (coverage 0%).

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

Purpose5/5

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

The verb 'Discover' clearly indicates the action, and 'new keyword ideas using Google Ads Keyword Planner' specifies the resource and purpose. It is distinct from sibling tools like get_keyword_performance or get_search_terms, which focus on existing data rather than generation of new ideas.

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

Usage Guidelines4/5

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

It provides explicit guidance on when to use include_monthly_volumes ('when the user asks about demand trends, seasonality, or 'when should I ramp budget'') and explains the two input modes (keywords or URL). However, it does not directly contrast with sibling tools for when this tool is the better choice.

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

Deploy Server