Skip to main content
Glama

Search terms report

search_terms_report
Read-only

Reveals the actual search terms that triggered your Google Ads, with matched keywords, cost, clicks and conversions per term—plus total spend on terms that never converted—for an account, campaign or ad group.

Instructions

What people actually searched before clicking the ads: each term with the keyword it matched, cost, clicks and conversions, sorted by cost, with totals for spend on terms that never converted. 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": "search_terms_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
limitNoTerms 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, open-world operation, so the bar is low. The description still earns credit by disclosing what comes back (field list), the sort order (by cost), and the presence of aggregate totals for zero-conversion spend — behavioral detail the annotations do not carry.

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?

Two sentences, no filler. The output content is front-loaded ahead of the scoping constraint, so an agent learns what it gets before it learns how to narrow it.

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

Completeness5/5

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

There is no output schema, so the description must characterize the return value — and it does, listing fields, sort order, and the zero-conversion totals. Combined with the fully documented input schema, an agent has enough to call this correctly and interpret the result.

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 coverage is 100%, so every parameter, including the campaign/ad group scoping and the cost-based limit, is already documented in the schema. The description's only added semantic is that the scope may be the whole account or narrowed to one campaign or ad group, which is marginal on top of the schema. Baseline 3 applies.

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?

Opens with a plain-language definition of the resource ('What people actually searched before clicking the ads') and then enumerates the returned fields: matched keyword, cost, clicks, conversions. That is specific enough to distinguish it from a keyword performance report without opening a schema.

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 scoping sentence ('Whole account, or one campaign or ad group') tells the agent how to narrow the call, which is useful context. But there is no explicit when-to-use guidance and no named alternative — nothing tells the agent to prefer keywords_report or search_console_opportunities under particular conditions.

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