Skip to main content
Glama
Sign In
get-mcp-ads

Google Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

google ads get search terms

google_ads_get_search_terms
Read-onlyIdempotent

Retrieve Google Ads search term performance by date range and campaign or ad group to see which queries drive clicks and conversions. Choose search term view or campaign insight reports.

Instructions

Fetch search term performance from search_term_view or campaign_search_term_insight depending on reportType.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
endDateYesEnd date YYYY-MM-DD
adGroupIdNoOptional ad group ID filter. Applies directly to search_term_view and via segments.ad_group for insight reports.
startDateYesStart date YYYY-MM-DD
campaignIdNoOptional campaign ID filter
customerIdYesGoogle Ads customer ID (without dashes, e.g., 1234567890)
reportTypeNoNative provider report type; determines supported metrics and dimensions.search_term_view
searchTermContainsNoOptional substring filter for search_term_view

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / adGroupId / $ref
      Removed value: -"#/properties/campaignId"
    • addedInput schema / properties / adGroupId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / adGroupId / type
      Added value: +"string"
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv2.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds the useful behavioral detail that results come from one of two report sources depending on reportType, but it does not add much beyond that regarding limits, report constraints, or execution behavior.

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?

The description is a single front-loaded sentence with no wasted language. It states the action, resource, and conditional source selection 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 a full input schema, output schema, and annotations, the description can be brief. However, for an eight-parameter reporting tool with two report modes, it does not fully explain when each mode is appropriate or how this differs from adjacent search-term and keyword-performance tools.

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 the schema already documents all eight parameters, including the reportType enum and conditional searchTermContains behavior. The description reinforces the reportType choice but does not add syntax or meaning beyond what the schema already provides.

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 uses a specific verb ('Fetch') and resource ('search term performance') and identifies the two underlying report types. It is clear what the tool does, but it does not explicitly distinguish itself from related siblings such as google_ads_get_paid_organic_search_terms or google_ads_get_keyword_performance.

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 notes that the source depends on reportType, but that is parameter behavior rather than guidance on when to choose this tool over alternatives. It provides no explicit when-to-use, when-not-to-use, or sibling-routing guidance.

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

Deploy Server

Other Tools