Google Analytics 4 by Get MCP Ads

ga4 get bigquery export diagnostics

ga4_get_bigquery_export_diagnostics

Read-onlyIdempotent

Detect GA4 BigQuery export links and diagnose export mode, stream coverage, excluded events, and dataset location for a property.

Instructions

Detect GA4 BigQuery export links and diagnose export modes, stream coverage, excluded events, and dataset location.

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)
`includeDataStreams`	No	Include data stream summaries to compare against BigQuery exportStreams

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.6/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 without help from the description. The description adds diagnostic scope (it reports excluded events and dataset location) but says nothing about behavior when no export link exists, whether it queries the BigQuery dataset directly, or latency implications of an open-world read.

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 front-loaded sentence with the detection action first and the diagnostic facets second; no filler, no restatement of the tool name or title.

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 definition covers enough for correct invocation. The remaining gap is behavioral edge cases — what the agent sees when no export link is configured — but that is partly mitigated by the output schema.

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%: both propertyId (numeric GA4 property ID) and includeDataStreams (include stream summaries to compare against exported streams) are documented in the schema. The description adds no parameter-level semantics beyond that, so baseline 3 applies.

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 pairs a specific verb ("Detect... and diagnose") with a precise resource (GA4 BigQuery export) and enumerates the facets it inspects: export modes, stream coverage, excluded events, and dataset location. That scope naturally separates it from sibling diagnostics tools such as ga4_get_ecommerce_diagnostics or ga4_get_server_side_tagging_diagnostics, though it never names a sibling explicitly.

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 purpose implies when to call it — you want to know whether a BigQuery export link exists and what it covers — but there is no explicit when-to-use statement, no stated prerequisites (e.g., admin/OAuth scope), and no guidance on alternatives if the agent just wants raw report data. Usage is inferable, not stated.

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