Google Analytics 4 by Get MCP Ads

ga4 list admin resources

ga4_list_admin_resources

Read-onlyIdempotent

List GA4 admin collections read-only: streams, custom definitions, key events, audiences, links, annotations, channel groups, expanded datasets, subproperty/rollup config, access bindings.

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

TableJSON 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

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description repeats 'read-only mode' but adds a useful nuance: only 'allowlisted' collections are supported. It does not disclose pagination, but the pageSize schema description covers that, so this is acceptable given the strong annotation coverage.

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 sentence with a front-loaded action ('List...') followed by a colon-led list of collections. It is efficient and structured, though the list overlaps heavily with the schema enum, making it slightly redundant. Still, it earns its place by giving an at-a-glance scope.

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 complete schema, a present output schema, and safety annotations, the description gives enough for an agent to invoke the tool correctly. The only notable gap is the lack of differentiation from specialized sibling getters, which is more of a usage-guidance issue than an invocation-correctness issue.

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 documents all four parameters, including the enum for 'collection' and the access-bindings-only note for includePersonalIdentifiers. The description's enumeration of resource types maps to enum values but adds only a human-readable summary, not new semantic detail. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and a specific resource ('allowlisted GA4 Admin collection'), and then enumerates the exact collection types it covers. This clearly differentiates it from the reporting/diagnostic sibling tools and tells an agent what it operates on.

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 given about when to use this tool versus specialized siblings such as ga4_get_custom_definitions, ga4_get_key_events, or ga4_get_channel_groups. The description implies a general admin-listing role but leaves the agent to infer the relationship between this generic list and the more targeted getters.

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