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 suggest geo targets

google_ads_suggest_geo_targets
Read-onlyIdempotent

Resolve up to 25 location names or geo target IDs to Google Ads geoTargetConstants, returning criterion IDs, canonical names, target types, status, parents, locale, and approximate reach.

Instructions

Resolve up to 25 location names or geo target IDs to Google Ads geoTargetConstants. Returns criterion IDs, canonical names, target types, status, parents, locale, and approximate reach. Read-only.

Input Schema

NameRequiredDescriptionDefault
localeNoLocale used for human-readable lookup results.en
countryCodeNoCountry code used to localize keyword or targeting results.
geoTargetIdsNoGoogle Ads geo-target constant IDs for the intended locations.
locationNamesNoHuman-readable location names for Google to resolve into geo-target constants.

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' is redundant. It adds the 25-item batch cap and enumerates return fields (criterion IDs, parents, approximate reach), which is modest extra value — though that shape is also covered by the output schema.

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?

Three short sentences, front-loaded with the verb and resource, then output shape, then safety. No filler and nothing buried.

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

Completeness4/5

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

Output schema and annotations carry return values and safety, so the description is nearly sufficient. The gap is that all four params are optional and two alternative input paths exist, yet the description doesn't say whether they can be combined or which takes precedence.

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 locale, countryCode, geoTargetIds and locationNames. The description restates the 25-item limit and the two input modes but adds no rules on precedence, exclusivity, or how locale/countryCode affect resolution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Resolve ... location names or geo target IDs to Google Ads geoTargetConstants', with the output shape enumerated. No sibling tool performs geo-target resolution, so an agent can route here without ambiguity.

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?

Usage is implied by the resolution framing, and the 'or' between names and IDs hints at two input paths, but it never states when to prefer this over e.g. google_ads_run_gaql with a geo_target_constant query, nor what happens if both input arrays are supplied. No explicit when-not 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