Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Keyword performance

get_keyword_performance

Read-only

Retrieve keyword performance metrics including quality score, impressions, clicks, CTR, CPC, and conversions. Use compact mode for summarized totals and top spenders.

Instructions

Get keyword metrics including quality scores and competitive data.

Returns: keyword text, match type, quality score, impressions, clicks, CTR, CPC, conversions for each keyword.

Set compact=true for audits/overviews: returns totals, match-type distribution, the top-10 spenders, low-quality-score keywords, and zero-conversion spenders instead of every row (~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.3/5.0

Behavior5/5

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

The description aligns with the read-only and non-destructive annotations and adds context by explaining that compact=true changes the return format to a summary. This goes beyond the annotations and clarifies expected behavior without contradiction.

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, with the purpose front-loaded, followed by return fields and the compact mode explanation. It avoids unnecessary fluff and communicates the essential information efficiently.

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?

The description provides a solid overview of functionality and return data, and the output schema likely covers detailed fields. However, it lacks context on parameter defaults and date handling, which would be helpful for full usability. Still, it is adequate for a read-only reporting tool.

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 description only explains the compact parameter, which is valuable, but provides no explanation for customer_id, date_range_start, or date_range_end. Given the schema has no descriptions (0% coverage), the description fails to add sufficient meaning for these parameters, leaving their format and semantics unclear.

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 identifies the tool's purpose as retrieving keyword metrics, specifically mentioning quality scores and competitive data. This distinguishes it from sibling tools like campaign or ad performance, making the resource and scope explicit.

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 a specific usage scenario (audits/overviews) with the compact=true option, giving concrete guidance on when to use the summary mode. However, it does not explicitly contrast with alternative tools like get_campaign_performance or get_search_terms, so some inference is required.

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

Deploy Server