Google Analytics 4 by Get MCP Ads

ga4 get metadata

ga4_get_metadata

Read-onlyIdempotent

Retrieves all dimensions and metrics available for a specified GA4 property, including custom definitions, so you can discover valid fields for reporting and queries.

Instructions

Get the complete list of dimensions and metrics available for a specific GA4 property. Useful for discovering custom dimensions/metrics.

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)

Output Schema

Name	Required	Description	Default
`result`	Yes	Original 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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

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"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered without description help. The description adds only the 'complete list' framing (results are exhaustive for the property) and nothing about scope limits, caching, or property-permission requirements.

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?

Two short sentences, front-loaded with the action and resource, then the use case. There is minor redundancy in the second sentence but no wasted text; slightly more structure would be needed for a 5.

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?

An output schema exists, so return-value detail is unnecessary, and rich annotations cover the behavior profile. The only meaningful gap is that an agent cannot tell from this text whether to prefer it over ga4_get_custom_definitions for custom-dimension discovery.

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

Parameters4/5

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

With a single parameter at 100% schema description coverage (including a numeric format example), the schema carries the burden entirely and the baseline of 3 is met. The description reinforces the property scoping ('for a specific GA4 property'), adding slight value over the schema.

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 ('Get') and resource ('complete list of dimensions and metrics') scoped to a GA4 property, which is concrete enough to act on. It stops short of distinguishing itself from the sibling ga4_get_custom_definitions, whose territory ('custom dimensions/metrics') it also claims, creating mild overlap 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?

The second sentence gives an implied use case (discovering custom dimensions/metrics), which suggests calling this before building report queries. However there is no explicit when-to-use/when-not-to-use guidance and no routing to ga4_get_custom_definitions or ga4_get_event_parameters, which cover adjacent discovery needs.

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