Google Analytics 4 by Get MCP Ads

ga4 get audience diagnostics

ga4_get_audience_diagnostics

Read-onlyIdempotent

Retrieve read-only audience diagnostics for a GA4 property to inspect audience definitions, recurring audience list details, and observed audience report data.

Instructions

Read-only audience diagnostics from Admin API audiences, Data API recurring audience lists, and observed audienceName report fallback.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	No	End date YYYY-MM-DD or relative (today, yesterday)
`startDate`	No	Start date YYYY-MM-DD or relative (7daysAgo, yesterday)
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.	last28days
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)
`includeDefinitions`	No	Include full Admin API audience definitions when available
`recurringAudienceListName`	No	Optional resource name, e.g. properties/123456789/recurringAudienceLists/abc123

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.2/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. The description usefully discloses the underlying data sources and a fallback behavior, which adds context beyond annotations. It does not cover authentication needs, rate limits, or what the diagnostics include.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though it could be slightly more structured by separating purpose from source details.

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?

The tool has annotations, an output schema, and complete parameter descriptions, so the description need not explain return values or every parameter. However, it remains thin on when to use this diagnostic tool versus its audience-related siblings, which is relevant context for a seven-parameter diagnostics endpoint.

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 all seven parameters are documented in the input schema. The description does not add parameter-specific meaning beyond saying the tool reads from several audience-related sources. Baseline 3 is appropriate when the schema already carries parameter semantics.

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 read operation and resource: audience diagnostics. It also identifies the three data sources (Admin API, recurring audience lists, report fallback), which helps distinguish it from general reporting tools. It does not explicitly differentiate it from the closely related audience export diagnostics sibling.

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?

The description gives no explicit guidance about when to use this tool versus alternatives such as ga4_get_audience_export_diagnostics or ga4_list_audience_exports. Usage is only implied by the word 'diagnostics' and the listed sources, with no when-not or prerequisite guidance.

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