Google Analytics 4 by Get MCP Ads

ga4 get property configuration

ga4_get_property_configuration

Read-onlyIdempotent

Read GA4 property details and selected Admin settings—attribution, data retention, Google Signals, reporting identity, or user-provided data—to inspect configuration for audits and setup checks.

Instructions

Read GA4 property details plus selected singleton Admin settings (attribution, retention, Google Signals, reporting identity, or user-provided-data settings).

Input Schema

Name	Required	Description	Default
`settings`	No	Property configuration surfaces to inspect.
`propertyId`	Yes	Numeric GA4 property ID or properties/{id}.

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.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered and the description does not contradict it. The description adds that the settings are 'singleton' Admin surfaces, hinting they are individual config objects rather than lists, but it says nothing about permission requirements, whether unrequested settings cost extra calls, or how missing/unsupported settings are surfaced. Adequate but thin beyond what annotations provide.

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?

A single sentence, front-loaded with the core read action and followed by the enumerated optional surfaces. Every clause carries information; 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.

Completeness4/5

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

An output schema exists, annotations cover the safety profile, and there are only two parameters, so the description needn't explain return values. It is nearly complete; the only real gap is the default/no-settings behavior and any permission caveat for Admin settings, which an agent would need before relying on it.

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 coverage is 100%, so both propertyId and settings are already documented, and the baseline is 3. The description restates the settings enum in human-readable terms and frames them as 'singleton', which is mild added meaning, but it never states the behavior when settings is left at its default empty array (presumably property details only) or whether requesting multiple settings is batched into one call.

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?

States a specific verb (read) and resource (GA4 property details), then enumerates the exact Admin surfaces it can return: attribution, retention, Google Signals, reporting identity, and user-provided-data settings. That enumeration separates it from the broad sibling ga4_list_admin_resources and from ga4_list_properties without requiring the agent to open either schema.

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 phrase 'plus selected ... settings' implies that the settings array is an opt-in extra on top of base property details, which is a usable usage hint. But there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., vs ga4_list_admin_resources or ga4_get_metadata), so the agent must infer the routing.

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