Skip to main content
Glama

Google_analytics

by io.github.pipeworx-io

Ga Run Report

ga_run_report
Read-onlyIdempotent

Query GA4 analytics data by dimensions (e.g., "city", "pagePath") and metrics (e.g., "activeUsers", "sessions") for a date range. Returns aggregated data rows with dimension and metric values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rows to return (default 100, max 10000)
metricsYesList of metric names (e.g., ["activeUsers", "sessions", "screenPageViews"])
end_dateYesEnd date (YYYY-MM-DD or relative: "today", "yesterday")
order_bysNoOptional ordering. Each item: { dimension: { dimensionName, orderType? } } or { metric: { metricName }, desc? }
dimensionsNoList of dimension names (e.g., ["city", "pagePath", "date"])
start_dateYesStart date (YYYY-MM-DD or relative: "today", "yesterday", "7daysAgo", "30daysAgo")
property_idYesGA4 property ID (numeric, e.g., "123456789")
dimension_filterNoOptional dimension filter object (GA4 FilterExpression format)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoAPI response kind identifier
rowsNoAggregated data rows with dimension and metric values
errorNoError code if connection not established
messageNoError message if connection not established
rowCountNoTotal number of rows returned
metricHeadersNoHeaders for metric columns in the report
dimensionHeadersNoHeaders for dimension columns in the report

Schema Changelog

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

  1. Changed9 schema fields changed
    • changedOutput schema / properties / dimensionHeaders / description
      Previous value: -"List of dimension names in the report"New value: +"Headers for dimension columns in the report"
    • changedOutput schema / properties / error / description
      Previous value: -"Error message if connection failed"New value: +"Error code if connection not established"
    • addedOutput schema / properties / kind
      Added value: +{
+  "description": "API response kind identifier",
+  "type": "string"
+}
    • changedOutput schema / properties / message / description
      Previous value: -"Error details if connection failed"New value: +"Error message if connection not established"
    • changedOutput schema / properties / metricHeaders / description
      Previous value: -"List of metric names and types in the report"New value: +"Headers for metric columns in the report"
    • changedOutput schema / properties / metricHeaders / items / properties / type / description
      Previous value: -"Metric data type"New value: +"Data type of metric"
    • changedOutput schema / properties / rows / description
      Previous value: -"Report data rows with dimension and metric values"New value: +"Aggregated data rows with dimension and metric values"
    • removedOutput schema / properties / rows / items / properties / dimensionValues / items / properties
      Removed value: -{
-  "value": {
-    "description": "Dimension value",
-    "type": "string"
-  }
-}
    • removedOutput schema / properties / rows / items / properties / metricValues / items / properties
      Removed value: -{
-  "value": {
-    "description": "Metric value",
-    "type": "string"
-  }
-}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "dimensionHeaders": {
+      "description": "List of dimension names in the report",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Dimension name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error details if connection failed",
+      "type": "string"
+    },
+    "metricHeaders": {
+      "description": "List of metric names and types in the report",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Metric name",
+            "type": "string"
+          },
+          "type": {
+            "description": "Metric data type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rowCount": {
+      "description": "Total number of rows returned",
+      "type": "number"
+    },
+    "rows": {
+      "description": "Report data rows with dimension and metric values",
+      "items": {
+        "properties": {
+          "dimensionValues": {
+            "description": "Dimension values for this row",
+            "items": {
+              "properties": {
+                "value": {
+                  "description": "Dimension value",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "metricValues": {
+            "description": "Metric values for this row",
+            "items": {
+              "properties": {
+                "value": {
+                  "description": "Metric value",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end_date": "today",
+    "metrics": [
+      "activeUsers",
+      "sessions"
+    ],
+    "property_id": "123456789",
+    "start_date": "30daysAgo"
+  },
+  {
+    "dimensions": [
+      "city",
+      "pagePath"
+    ],
+    "end_date": "2024-01-31",
+    "limit": 500,
+    "metrics": [
+      "screenPageViews",
+      "bounceRate"
+    ],
+    "order_bys": [
+      {
+        "desc": true,
+        "metric": {
+          "metricName": "screenPageViews"
+        }
+      }
+    ],
+    "property_id": "123456789",
+    "start_date": "2024-01-01"
+  }
+]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context by stating that the result is 'aggregated data rows with dimension and metric values,' which clarifies the return shape beyond the 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 a single, front-loaded sentence that efficiently states the action, resource, key parameter categories, and return type. It includes useful examples without any filler or redundancy, making it highly concise and well-structured.

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 8 parameters, 4 required, nested objects, and 100% schema coverage, the schema carries most of the burden, and an output schema exists to define return values. The description provides sufficient high-level framing for a GA4 report tool, but slightly more explicit usage guidance would make it fully complete.

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 schema descriptions cover all 8 parameters with examples and formats, so the baseline is 3. The prose description adds only general context about dimensions and metrics (e.g., 'city', 'pagePath', 'activeUsers', 'sessions') but does not meaningfully enhance the parameter-level details already present in the schema.

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 uses a specific verb 'Query' and clearly identifies the resource as GA4 analytics data with dimensions, metrics, and a date range, which returns aggregated rows. This content distinguishes it from sibling GA4 tools like ga_get_realtime and ga_get_metadata by emphasizing historical, report-style data retrieval.

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 description does not explicitly state when to use this tool versus alternatives, nor does it name exclusions. However, the mention of 'for a date range' implies it is for historical GA4 reporting rather than realtime or metadata queries, so the usage context is only weakly implied.

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