Google Analytics 4 by Get MCP Ads

ga4 list admin resources

ga4_list_admin_resources

Read-onlyIdempotent

Lists read-only GA4 Admin resources for a property—streams, custom definitions, key events, audiences, links, annotations, channel groups, and access bindings—to inspect configuration and permissions.

Instructions

List an allowlisted GA4 Admin collection in read-only mode: streams, custom definitions, key events, audiences, product links, annotations, channel groups, expanded datasets, subproperty/rollup configuration, and access bindings.

Input Schema

Name	Required	Description
`pageSize`	No	Maximum items requested per page. Follow the returned pagination information for remaining results.
`collection`	Yes	Allowlisted administrative resource collection to read.
`propertyId`	Yes	Numeric GA4 property ID or properties/{id}.
`includePersonalIdentifiers`	No	Access bindings only. Explicitly include user/email identifiers; 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

A3.5/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 'read-only mode' is largely redundant restatement. The genuinely additive context is the 'allowlisted' constraint — only a fixed set of collections is reachable — which tells the agent requests outside the enum will fail. Pagination behavior and the personal-identifier redaction default are left to the schema.

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?

A single front-loaded sentence that puts the verb, resource and read-only constraint first, then enumerates scope. The long trailing list earns its place by pre-signalling which collections exist, though it is dense enough to be slightly hard to scan.

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, a 100%-documented schema, and an output schema, the description only needs to establish scope and safety, which it does. The absence of routing guidance versus the specialized getter siblings is the one meaningful gap for a tool in this crowded family.

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 already explains propertyId formats, the collection enum, pageSize limits, and the includePersonalIdentifiers redaction default. The description's enumeration of collections loosely mirrors the enum but adds no operational detail beyond it, 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?

States a specific verb ('List') and resource ('allowlisted GA4 Admin collection') and enumerates the covered collections, so an agent knows exactly what domain it touches. It stops short of naming the overlapping siblings (ga4_get_custom_definitions, ga4_get_key_events, ga4_get_channel_groups), so the boundary between this generic lister and those specialized getters is not explicitly drawn.

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?

'read-only mode' and 'allowlisted' imply this is a safe read path for administrative config, giving implied usage context. However there is no explicit guidance on when to pick this generic lister over the sibling-specific getters that read the same collections, nor any prerequisite or exclusion statements.

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