Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Search terms report

get_search_terms

Read-only

Retrieve search terms report showing actual user queries to identify negative keywords and understand search intent, with optional compact summary for quick insights.

Instructions

Get search terms report — what users actually typed before clicking your ads.

Critical for finding negative keyword opportunities and understanding user intent. Returns: search term, campaign, ad group, impressions, clicks, conversions.

Set compact=true for audits/overviews: returns totals, the top-10 terms by clicks, ready-made negative-keyword waste candidates (5+ clicks, zero conversions), and top converters (~90% smaller).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`compact`	No
`customer_id`	No
`date_range_end`	No
`date_range_start`	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 / compact
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv0.9.0Jun 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare the tool as read-only and non-destructive, which the description does not contradict. The description adds behavioral context about the data source (what users typed) and the nature of the report, going slightly beyond the annotations without needing to restate safety attributes.

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

Conciseness5/5

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

The description is concise and well-structured: it opens with a clear definition, adds a meaningful use-case rationale, lists return fields in a compact line, and then explains the compact mode with specific examples. No unnecessary filler or redundancy is present, and the formatting aids quick comprehension.

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?

Given the large sibling list of reporting and management tools, this description provides enough context to distinguish itself—'search terms' is a specific concept and the focus on negative keywords clarifies its niche. However, it does not mention any prerequisites, required inputs, or limitations, which could leave an agent uncertain if all fields are always populated or if date ranges are mandatory.

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?

The schema lists four parameters but provides no descriptions for them (0% coverage). The description only explains the behavior of the 'compact' parameter (set to true for audits), leaving customer_id and date range parameters completely undocumented. This is a significant gap that forces the agent to infer their meaning from context.

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 description clearly states that the tool fetches a search terms report, explaining exactly what it returns (search term, campaign, ad group, impressions, clicks, conversions). It also explicitly ties the tool to negative keyword discovery and user intent analysis, making its purpose unambiguous and distinct from sibling reporting tools.

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?

The description provides strong usage context by stating the tool is 'critical for finding negative keyword opportunities' and explains when to use the compact mode (for audits/overviews). However, it does not explicitly name alternative tools or specify when not to use it, so it falls slightly short of full guidance.

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

Deploy Server