Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ga_run_report

Read-only

Run custom GA4 reports with chosen dimensions and metrics, plus filters, sorting, and two-date-range comparisons, to analyze website and app performance.

Instructions

Run a custom GA4 report with any dimensions/metrics (see ga_get_metadata for names). Supports filters, ordering, comparison of two date ranges.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "propertyId": "<propertyId>",
      "metrics": "<metrics>"
    },
    "name": "ga_run_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
limitNo
offsetNo
endDateNoyesterday
metricsYes
orderByNoDimension or metric name to sort by
startDateNoYYYY-MM-DD, or 'today', 'yesterday', 'NdaysAgo'28daysAgo
dimensionsNo
propertyIdYes
metricFiltersNo
compareEndDateNo
compareStartDateNo
dimensionFiltersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, open-world operation, and the description adds that it supports filters, ordering, and two-range comparison. It does not disclose rate limits, cost/performance considerations, or how missing dates and pagination behave, so it adds only moderate behavioral context.

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 definition is compact and front-loaded with the core action, and every clause contributes to the functional scope. It is perhaps too terse for a complex reporting tool, but there is no wasted wording.

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

Completeness2/5

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

This is a complex query tool with 13 parameters, low schema description coverage, nested filter objects, and no output schema. The description does not explain return shape, pagination, date semantics, or how dimensionFilters differ from metricFilters, leaving significant gaps for an agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 15% across 13 parameters, so the description must carry substantial explanatory weight. It names the broad categories of dimensions, metrics, filters, ordering, and comparison, but leaves propertyId, date formats, limit/offset pagination, desc, and detailed filter semantics undocumented.

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?

The description uses a specific verb and resource: 'Run a custom GA4 report with any dimensions/metrics'. This clearly distinguishes it from metadata lookup and implies it is the flexible/custom reporting path, though it does not explicitly contrast with ga_overview or ga_realtime.

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?

It gives one useful routing hint by pointing to ga_get_metadata for dimension and metric names. However, it does not state when to use this tool instead of ga_overview or ga_realtime, nor does it describe prerequisites or practical limits.

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