Google Analytics 4 by Get MCP Ads

ga4 query audience export

ga4_query_audience_export

Read-onlyIdempotent

Query rows from an existing GA4 Audience Export to retrieve audience data; user/device identifiers stay redacted unless explicitly opted in.

Instructions

Query rows from an existing GA4 Audience Export. User/device identifiers are redacted by default; include them only through explicit opt-in.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`offset`	No	Zero-based number of rows to skip before returning results.
`audienceExportName`	Yes	Full GA4 audience-export resource name returned by list_audience_exports.
`includePersonalIdentifiers`	No	Explicitly return user/device identifiers. False redacts identifier columns 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.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

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

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds a meaningful privacy trait not in annotations: identifiers are redacted by default and only returned via explicit opt-in. It could say more about output handling or rate limits, but the core behavioral addition is present.

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 sentences with zero waste. The core purpose is front-loaded, followed immediately by the important privacy caveat.

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?

With rich annotations, an output schema, and fully documented parameters, the description covers purpose and the key privacy behavior. The only meaningful gap is the absence of explicit routing guidance to or from sibling tools such as ga4_list_audience_exports.

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 fully documents all four parameters. The description only restates the redaction default for includePersonalIdentifiers, adding no new parameter semantics beyond what the schema already states.

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 states a specific verb (Query) and resource (rows from an existing GA4 Audience Export), which clearly separates it from listing exports or running reports. However, it does not explicitly name or contrast with sibling tools like ga4_list_audience_exports or ga4_get_audience_export_diagnostics.

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 'existing GA4 Audience Export' implies a prerequisite, and the required audienceExportName parameter's schema description points to list_audience_exports. But the description itself offers no explicit when-to-use guidance, exclusions, or alternative tool comparisons.

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