Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Keyword performance

get_keyword_performance
Read-only

Retrieve Google Ads keyword performance metrics—quality score, impressions, clicks, CTR, CPC, conversions—to audit spend, flag low-quality or zero-conversion keywords, and compare match types.

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.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compactNoWhen 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).
customer_idNoGoogle Ads customer ID, digits with or without dashes (e.g. "123-456-7890"). Defaults to the configured ads.customer_id.
date_range_endNoEnd date as "YYYY-MM-DD" (inclusive).
date_range_startNoStart date as "YYYY-MM-DD". Both dates must be set to apply a range; if either is empty, the last 30 days are used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.27.1
    • addedInput schema / properties / compact / description
      Added value: +"When true (for audits/overviews), returns totals, match-type\ndistribution, the top-10 spenders, low-quality-score keywords, and\nzero-conversion spenders instead of every row (~90% smaller)."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID, digits with or without dashes\n(e.g. \"123-456-7890\"). Defaults to the configured ads.customer_id."
    • addedInput schema / properties / date_range_end / description
      Added value: +"End date as \"YYYY-MM-DD\" (inclusive)."
    • addedInput schema / properties / date_range_start / description
      Added value: +"Start date as \"YYYY-MM-DD\". Both dates must be set\nto apply a range; if either is empty, the last 30 days are used."
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  5. First observedv0.9.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the content scope (quality scores and competitive data) but says nothing about pagination, rate limits, or auth requirements beyond the doc link, so it adds only modest context on top of the structured data.

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?

Front-loaded with the core purpose in the opening clause, followed by a compact return-value list and a doc link. Every sentence is short and earns its place, though the field enumeration is partly redundant given an output schema exists.

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?

With an output schema present, the return-value listing is not strictly necessary, and annotations cover safety; full schema coverage handles the parameters. The only real gap is the absence of sibling differentiation, which the description does not address.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters (compact, customer_id, date_range_start/end) are fully documented in the schema, including the compact-mode behavior and the 30-day default. The description adds no parameter detail; baseline 3 applies.

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?

States a specific verb+resource ("Get keyword metrics including quality scores and competitive data") and enumerates the returned fields (keyword text, match type, quality score, impressions, clicks, CTR, CPC, conversions). It is clearly keyword-level reporting, though it never explicitly contrasts itself with siblings like get_search_terms or get_campaign_performance, so the distinction is inferred rather than stated.

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

Usage Guidelines2/5

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

No when-to-use statement, no prerequisites, and no routing to or from alternatives such as get_search_terms, get_campaign_performance, or get_ad_performance. Usage is only implied by the topic, leaving the agent to guess which performance tool to pick.

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

Deploy Server

Other Tools