Skip to main content
Glama
Sign In
Google Ads by Get MCP Ads

Google Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

google ads get paid organic search terms

google_ads_get_paid_organic_search_terms
Read-onlyIdempotent

Retrieves paid and organic search terms for a Google Ads customer, with optional filters, and falls back to paid-only data when organic fields are unavailable.

Instructions

Read-only paid/organic search terms report. Uses paid_organic_search_term_view when available and falls back to paid-only search_term_view if organic fields are unavailable.

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
serpTypeNoOptional search engine results page type segment filter
adGroupIdNoOptional ad group ID filter
startDateYesStart date YYYY-MM-DD
campaignIdNoOptional campaign ID filter
customerIdYesGoogle Ads customer ID (without dashes, e.g., 1234567890)
searchTermContainsNoOptional search term substring filter

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

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value by disclosing the view-selection fallback, which affects what fields the agent may receive. It stops short of saying whether the fallback silently drops organic columns or signals it in the response, which would have been ideal.

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 waste, with the read-only/scope statement front-loaded and the fallback caveat second. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values needn't be described, and parameters are fully covered. What is missing for a report tool sitting next to a near-identical sibling is the disambiguation and the consequence of the fallback on the result shape.

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 every parameter including the serpType enum and date patterns is documented in the schema itself. The description adds no parameter meaning beyond that, which is the baseline-3 case.

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 and resource ('Read-only paid/organic search terms report') plus the view it reads, so the agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling google_ads_get_search_terms, which sounds nearly identical.

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 fallback sentence explains an internal implementation detail but gives no guidance on when to pick this over google_ads_get_search_terms or the generic google_ads_run_gaql. No prerequisites (customer ID format, permissions) or exclusion conditions are stated beyond 'read-only'.

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