Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_search_terms

Read-only

Retrieve Google Ads search terms with cost and conversions to identify wasted spend and discover new keywords; filter by date range, campaign, or minimum cost.

Instructions

Search terms report: the actual queries that triggered ads, with cost and conversions (find wasted spend and new keywords).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNo
minCostNo
dateRangeNoLAST_30_DAYS
startDateNoYYYY-MM-DD; overrides dateRange when used with endDate
campaignIdNo
customerIdYesGoogle Ads customer ID (with or without dashes)
loginCustomerIdNoManager (MCC) ID if accessing through a manager; defaults to ads.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so an agent knows this is a safe read operation against external ad data. The description adds that the returned rows contain cost and conversions, which is useful return-context information, but it says nothing about pagination, the default limit of 300, the maximum of 900, or how dateRange and startDate interact.

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?

A single sentence with the resource and return contents front-loaded, followed by a compact parenthetical on the use case. Nothing is wasted, and no filler is present.

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?

For an 8-parameter read tool with no output schema, the description is adequate at the level of purpose and return contents. It is incomplete, however, on filtering behavior (minCost, campaignId), pagination through limit, and date-range precedence (startDate/endDate overriding dateRange); an agent calling this correctly needs some of that information.

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

Parameters2/5

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

Schema description coverage is only 38% across 8 parameters. The description gives no parameter-level meaning at all. Several parameters are undocumented in both the schema and the description: minCost is especially relevant to "wasted spend," yet its threshold semantics are unexplained, and the same is true of campaignId, dateRange, and limit. The description does not compensate for the coverage gap.

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 names a specific resource ("Search terms report") and identifies the concrete contents: "the actual queries that triggered ads, with cost and conversions." That distinguishes it from sibling performance tools such as ads_keyword_performance, but it does not explicitly say how it differs from ads_query, so this falls short of a 5.

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 parenthetical "find wasted spend and new keywords" implies the intended use cases, but it does not state when to choose this tool over ads_keyword_performance or ads_query, nor does it list any exclusions or prerequisites. The guidance is only implied, not explicit.

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