Google Analytics 4 by Get MCP Ads

ga4 get audience export diagnostics

ga4_get_audience_export_diagnostics

Read-onlyIdempotent

Lists GA4 audience exports with state counts and optionally samples rows to diagnose export status and contents.

Instructions

Read-only Audience Export diagnostics. Lists existing audience exports, state counts, and optionally samples rows from an existing export.

Input Schema

Name	Required	Description
`pageSize`	No	Maximum items requested per page. Follow the returned pagination information for remaining results.
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)
`sampleLimit`	No	Maximum records included in the diagnostic sample.
`includeRowSample`	No	If true, query a small row sample from audienceExportName. Can include user-level export dimensions.
`audienceExportName`	No	Optional resource name, e.g. properties/123456789/audienceExports/abc123
`includePersonalIdentifiers`	No	Explicitly include user/device identifiers in the optional sample. False redacts them by default.

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

B3/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 the safety profile is covered; the description mostly restates read-only. It does add one useful behavioral note: that a row sample is optional and that 'state counts' are returned, but says nothing about permissions, quota cost, or what the diagnostics actually reveal beyond listing.

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 short, front-loaded sentences with no filler; the core action is stated first and the optional sampling capability second. Nothing is redundant or bloated.

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 and annotations plus a fully documented schema carry most of the load. But for a diagnostics tool in a crowded GA4 diagnostics family with overlapping list/query siblings, the description omits the one thing an agent most needs: how this differs from ga4_list_audience_exports, ga4_query_audience_export, and ga4_get_audience_diagnostics.

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 every parameter is already documented in the schema, including includeRowSample, includePersonalIdentifiers, and audienceExportName. The description's phrase 'optionally samples rows from an existing export' loosely maps to includeRowSample/audienceExportName but adds no syntax or semantics beyond the schema, so baseline 3 applies.

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

Purpose3/5

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

The description names a concrete verb set (lists, counts, samples) for the Audience Export resource, so the tool's own purpose is understandable. However, it does not distinguish itself from siblings that appear to do the same things: ga4_list_audience_exports (listing) and ga4_query_audience_export (row sampling). An agent reading only this text cannot tell why it should pick this tool over those two.

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 when-to-use guidance and no exclusion of alternatives, despite heavy apparent overlap with ga4_list_audience_exports, ga4_query_audience_export, and ga4_get_audience_diagnostics. The reader is left to infer selection criteria from nothing.

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