Skip to main content
Glama

Keywords report

keywords_report
Read-only

Retrieve Google Ads keyword status, match type, Quality Score, bids, and performance for an account, campaign, or ad group, including why keywords are not serving and negative keywords.

Instructions

The account's keywords with match type, status and why one isn't serving, Quality Score and its three parts, bid, and results in the window, plus ad-group negative keywords. Whole account, or one campaign or ad group.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>"
    },
    "name": "keywords_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
limitNoKeywords to list, by cost
ad_group_idNoOnly this ad group (from campaign_details)
campaign_idNoOnly this campaign (campaign_id from account_overview)
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)
include_pausedNoAlso list paused keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A3.5/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 the safety profile is covered. The description adds useful content-level disclosure (diagnostic 'why one isn't serving', Quality Score breakdown, negative keywords included), but says nothing about result truncation — the default limit of 100 keywords ordered by cost materially shapes what the agent sees and is only documented in the schema.

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?

Two sentences, no filler, and the payload contents are front-loaded ahead of the scoping note. The field enumeration is dense but each item earns its place by telling the agent what will come back from a tool with no output schema.

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 six parameters, no output schema and no nested objects, the description correctly shoulders the burden of describing the returned fields, which it does thoroughly. The remaining gap is operational (default top-100-by-cost truncation and paused exclusion), which the schema covers, so the definition is close to complete for an agent to call it correctly.

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 every parameter including days, limit, customer_id and include_paused is already documented with provenance hints. The description only loosely reinforces scoping ('whole account, or one campaign or ad group') and the time window ('in the window'), which is roughly baseline value for a fully-described schema.

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 enumerates exactly what the report contains — match type, status, non-serving reason, Quality Score and its three components, bid, window results, plus ad-group negatives — which is far more specific than the title 'Keywords report'. It does not explicitly distinguish itself from sibling reports such as ads_report or search_terms_report, leaving the agent to infer the keyword-level vs. ad-level vs. query-level split from names alone.

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?

The final sentence ('Whole account, or one campaign or ad group') implies the three scoping modes an agent can choose between, which is genuine usage context. However, there is no explicit when-to-use or when-not guidance relative to alternatives, and no mention that paused keywords are excluded unless include_paused is set — a decision point the agent must discover from the schema.

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