Google Analytics 4 by Get MCP Ads

ga4 get audience export diagnostics

ga4_get_audience_export_diagnostics

Read-onlyIdempotent

Diagnose Google Analytics 4 audience exports by listing existing exports and state counts. Optionally sample rows from any specified export to inspect data and identifiers.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description reiterates the readOnlyHint and adds modest behavioral specifics: it lists state counts and optionally samples rows from an existing export. It doesn't explain side effects, but the annotations already cover read-only, idempotent, and non-destructive behavior, so the description adds context without contradicting them.

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 concise sentences are front-loaded with the read-only diagnostics nature and then the capabilities. There is no filler, no restating of the obvious name, and no redundant detail.

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 a full input schema and an output schema present, the description needs only to orient the agent, which it does. The only real gap is the lack of guidance on when to use this diagnostic versus the similarly named list/query siblings.

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?

The input schema already documents all six parameters with descriptions (100% coverage), so the description is not responsible for parameter semantics. It mentions 'optionally samples rows' and 'existing export', reinforcing sampleLimit and audienceExportName, but adds no new parameter-level meaning.

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 uses a specific verb ('Lists') and identifies a clear resource ('existing audience exports, state counts') with an optional sampling behavior. It distinguishes itself from a generic reporting/query tool through the 'diagnostics' framing, though it doesn't explicitly name sibling tools that overlap.

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?

No guidance is provided on when to choose this diagnostic over ga4_list_audience_exports or ga4_query_audience_export. The description simply lists capabilities; the agent must infer that diagnostics are for troubleshooting. There are no explicit exclusions or fallback instructions.

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