Google Analytics 4 by Get MCP Ads

ga4 list accounts

ga4_list_accounts

Read-onlyIdempotent

List raw GA4 Analytics Admin accounts accessible to the authenticated user, with read-only auto-pagination for account discovery and access checks.

Instructions

List raw GA4 Analytics Admin accounts accessible to the authenticated user (read-only, auto-paginated).

Input Schema

Name	Required	Description	Default
`pageSize`	No	Maximum items requested per page. Follow the returned pagination information for remaining results.

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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds real value beyond them: "accessible to the authenticated user" discloses the auth-scoping rule and "auto-paginated" tells the agent it will not have to loop manually — a behavior the single pageSize parameter alone would not convey.

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 no filler. Scope, access constraint and pagination behavior are packed into one clause sequence, and nothing is redundant with the 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?

An output schema exists, so return values need not be described, and the description covers scope, auth and pagination for a zero-required-parameter list tool. The only meaningful omission is its position in the workflow relative to ga4_list_admin_resources and ga4_list_properties.

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 coverage is 100% and there is only one optional parameter (pageSize), which the schema fully documents including default 200 and max 200. The description's "auto-paginated" implies the agent need not manage paging, but it adds no syntax or semantics beyond the schema, so the 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?

Specific verb+resource: "List raw GA4 Analytics Admin accounts" scoped to "accessible to the authenticated user". This distinguishes it from report-running siblings like ga4_run_report, though it does not explicitly contrast with the adjacent ga4_list_admin_resources or ga4_list_properties, which an agent could plausibly confuse it with.

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?

Usage is only implied: an agent can infer this is the discovery step for account IDs, but nothing states when to pick it over ga4_list_admin_resources or ga4_list_properties, and no prerequisites or follow-up steps are given. Adequate but with a clear routing gap in a crowded list/get sibling set.

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