Skip to main content
Glama

MetricPort

Search terms report

ads_search_terms
Read-onlyIdempotent

Actual search terms that triggered ads, with cost, clicks, impressions and conversions. Default last 30 days, top 200 by cost.

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": {
      "property": "<property>"
    },
    "name": "ads_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNo
campaignNoCampaign name filter (contains)
propertyYesGoogle Ads customer id from list_properties, e.g. 1234567890
startDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the default lookback window and the cost-based ranking, but says nothing about pagination, result caps, or how limits interact with the ranking.

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, zero padding, and the metric list and defaults are front-loaded so the agent sees scope and default behavior immediately.

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

Completeness3/5

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

With no output schema, the description does list the returned metrics and defaults, but with 5 parameters, 40% schema coverage and no success/limit behavior documented, an agent still lacks guidance on filtering and result volume for a genuinely complex report.

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 40%: campaign and property are documented in the schema while startDate/endDate and limit are not. The description partially compensates by revealing the date default and that results are ordered by cost, which the schema does not state, but it adds nothing about the campaign filter or the interaction between limit and date range.

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 resource (actual search terms that triggered ads) plus the metrics returned, which separates it from sibling keyword/keyword-target reports like ads_keyword_performance. It stops short of explicitly naming the sibling it differs from, so an agent must infer the distinction.

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?

The description gives defaults (last 30 days, top 200 by cost) but never says when to use this report versus alternatives such as ads_keyword_performance, ads_query, or ads_wasted_spend. No prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.