Skip to main content
Glama
flin-google-ads-mcp

flin-google-ads-mcp

by flin-agency

get_search_terms

Read-only

Retrieve search-term-level entities and performance metrics from Google Ads, filtered by campaign, ad group, status, or date range.

Instructions

Get search-term-level entities and performance metrics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoALL
end_dateNo
date_rangeNoLAST_30_DAYS
start_dateNo
ad_group_idNo
campaign_idNo
customer_idNo
segment_by_dateNo
login_customer_idNo
conversion_action_idNo
conversion_action_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

C2.6/5.0
Behavior2/5

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

The readOnlyHint/destructiveHint=false annotations already establish that this is a safe read, so the description adds little on the safety axis. It says nothing about pagination via limit, default date_range behavior, or whether omitted filters widen results, which are the behaviors an agent actually needs here.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is not achieved through padding, but it leaves the definition thin rather than dense with useful signal.

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

Completeness2/5

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

With 12 parameters, no required fields, and 0% schema description coverage, a one-sentence description is well short of what an agent needs to call this correctly. An output schema covers return values and annotations cover safety, but the filtering and segmentation surface is entirely unexplained.

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

Parameters1/5

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

All 12 parameters have zero schema description coverage, and the description mentions none of them — not date_range/start_date/end_date, not segment_by_date, not campaign_id/ad_group_id scoping, not limit. It does nothing to compensate for the complete absence of parameter documentation.

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 (get) and resource (search-term-level entities) plus the fact that performance metrics are returned, which is enough for an agent to know what it retrieves. It offers no contrast with siblings such as get_keywords, so the keyword-vs-search-term distinction is left to inference.

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?

There is no when-to-use guidance, no mention of when an alternative such as get_keywords or get_insights would be preferred, and no note of prerequisites like needing a customer_id. The agent must guess the selection criteria entirely.

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