Skip to main content
Glama

Google_analytics

by io.github.pipeworx-io

Ga List Properties

ga_list_properties
Read-onlyIdempotent

List all GA4 properties you can access. Returns property IDs, names, creation dates, and account info. Use to find the property ID for ga_run_report queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNoMaximum number of account summaries to return (default 50)
page_tokenNoToken for fetching the next page of results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection not established
messageNoError message if connection not established
nextPageTokenNoToken for fetching next page of results
accountSummariesNoList of account summaries with accessible properties

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • changedOutput schema / properties / accountSummaries / description
      Previous value: -"List of accessible GA4 account and property summaries"New value: +"List of account summaries with accessible properties"
    • removedOutput schema / properties / accountSummaries / items / properties / propertySummaries / items / properties / parent
      Removed value: -{
-  "description": "Parent account",
-  "type": "string"
-}
    • addedOutput schema / properties / accountSummaries / items / properties / propertySummaries / items / properties / propertyType
      Added value: +{
+  "description": "Type of property",
+  "type": "string"
+}
    • changedOutput schema / properties / error / description
      Previous value: -"Error message if connection failed"New value: +"Error code if connection not established"
    • changedOutput schema / properties / message / description
      Previous value: -"Error details if connection failed"New value: +"Error message if connection not established"
    • changedOutput schema / properties / nextPageToken / description
      Previous value: -"Token for fetching next page"New value: +"Token for fetching next page of results"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accountSummaries": {
+      "description": "List of accessible GA4 account and property summaries",
+      "items": {
+        "properties": {
+          "account": {
+            "description": "Account resource name",
+            "type": "string"
+          },
+          "accountDisplayName": {
+            "description": "Display name of the account",
+            "type": "string"
+          },
+          "name": {
+            "description": "Account summary resource name",
+            "type": "string"
+          },
+          "propertySummaries": {
+            "description": "Properties under this account",
+            "items": {
+              "properties": {
+                "displayName": {
+                  "description": "Property display name",
+                  "type": "string"
+                },
+                "name": {
+                  "description": "Property resource name",
+                  "type": "string"
+                },
+                "parent": {
+                  "description": "Parent account",
+                  "type": "string"
+                },
+                "property": {
+                  "description": "Property ID",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error details if connection failed",
+      "type": "string"
+    },
+    "nextPageToken": {
+      "description": "Token for fetching next page",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "page_size": 50
+  }
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint), and the description adds useful context about the accessibility scope ('properties you can access') and the specific return fields, going beyond the structured annotations.

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?

The description is two sentences, front-loaded with the core action, and every sentence earns its place by adding return-value details and a practical use case. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a simple list operation, full schema parameter coverage, an output schema present, and annotations indicating safety, the description is complete. It covers what the tool does, what it returns, and the typical use case without leaving significant gaps.

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?

The input schema's descriptions cover 100% of parameters (page_size and page_token), so the description does not need to re-explain them. It adds no additional parameter-level detail, which aligns with the baseline for full schema coverage.

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 clearly states 'List all GA4 properties you can access', identifying the exact resource and verb. It also specifies the returned data (property IDs, names, creation dates, account info) and distinguishes its purpose from sibling analytics tools by directing users to use it to find property IDs for ga_run_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use the tool ('Use to find the property ID for ga_run_report queries'), providing clear context. However, it does not mention when not to use it or name alternative tools, falling short of the highest bar for exclusions.

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

All Google_analytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx and ask_pipeworx_beta are explicitly identical, ask_pipeworx_grounded and deep_research both route queries to the same 5,529 tools, and ai_visibility_check vs scan_competitor_ai_presence are near-duplicates. Only the small ga_* subset is clearly distinct.

Naming Consistency2/5

Conventions are mixed: GA tools use a ga_ prefix, but the majority use arbitrary names like ask_pipeworx, deep_research, remember, scan_dependency, and polymarket_arbitrage. No consistent verb_noun pattern across the set.

Tool Count2/5

35 tools is heavy, and the vast majority (31) are unrelated Pipeworx utilities rather than Google Analytics functionality. Only 4 tools actually serve the stated GA purpose, making the count inappropriate for the server name.

Completeness2/5

For Google Analytics, the surface is minimal: list properties, metadata, realtime, and run report—no property management, user management, or data mutation. As a Pipeworx toolkit it's broad but lacks full lifecycle coverage for any single domain.

Resources