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 recommendations

google_ads_get_recommendations
Read-onlyIdempotent

List Google Ads recommendations with type, resource, campaign/ad group links, dismissed status, and impact details to identify account optimization actions.

Instructions

List Google Ads recommendations with type, resource, campaign/ad group links, dismissed state, and impact when supported.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
customerIdYesGoogle Ads customer ID (without dashes, e.g., 1234567890)
typeFilterNoOptional RecommendationType enum filter
includeDismissedNoInclude recommendations already dismissed in the account.

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. Changed2 schema fields changedv2.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds only a vague 'impact when supported' caveat and says nothing about pagination behavior (the 1000-row cap), rate limits, or latency — leaving little value beyond the structured fields.

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?

It is a single front-loaded sentence that identifies the resource first and then the fields returned, with no filler. It could be slightly tighter, but every clause maps to a real output field.

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 do not need explaining, and the tool is a simple read. However, the absence of any when-to-use routing versus run_gaql or account-resolution prerequisite leaves the definition only minimally complete for an agent operating among 30+ siblings.

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 all four parameters are already documented in the schema, including the limit bounds, the enum pattern for typeFilter, and the includeDismissed default. The description's mention of 'dismissed state' and 'type' merely echoes those parameters without adding format or semantic detail, so the baseline 3 applies.

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 gives a specific verb and resource ('List Google Ads recommendations') and enumerates the payload contents (type, resource, campaign/ad group links, dismissed state, impact). This clearly distinguishes it from resource-specific siblings like get_campaigns or get_adgroups, though it never explicitly contrasts with the generic google_ads_run_gaql, which could also return recommendation data.

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 guidance on when to choose this tool over google_ads_run_gaql or the other get_* tools, and no stated prerequisites (e.g., that a customerId must be resolved via google_ads_list_accounts first). The includeDismissed and typeFilter behavior is implied by the parameter names only, not explained as usage strategy.

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