Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ga_overview

Read-only

Summarize Google Analytics 4 performance by dimension, including users, sessions, engagement, key events, and revenue for a chosen date range.

Instructions

Quick GA4 performance summary: users, new users, sessions, engagement rate, avg session duration, views, key events (conversions) and revenue, broken down by a chosen dimension.

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>"
    },
    "name": "ga_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNoyesterday
breakdownNochannel
startDateNoYYYY-MM-DD, or 'today', 'yesterday', 'NdaysAgo'28daysAgo
propertyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the concrete metric set and the fact that results are split by a dimension, but says nothing about defaults (28-day window, limit 25), sampling, or pagination behavior.

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?

A single front-loaded sentence that leads with the tool's role and then lists outputs; no filler or redundancy. It is compact enough that the metric enumeration does not feel bloated.

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

Completeness3/5

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

With no output schema, the description usefully compensates by naming the returned metrics and the dimension split. However, for a 5-parameter tool at 20% schema coverage it still omits parameter guidance (limit, endDate format, propertyId source), so it is adequate rather than complete.

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 20% — just startDate is documented inline. The description explains the 'breakdown' idea ('broken down by a chosen dimension') but adds no meaning for limit, endDate, or the required propertyId, leaving most parameters to be inferred from bare enum/default values.

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 names a specific verb+resource ('Quick GA4 performance summary') and enumerates the exact metrics returned (users, sessions, engagement rate, key events, revenue) plus the dimension breakdown. That is enough to distinguish it from a generic report runner like ga_run_report, though it never names that sibling explicitly.

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 word 'Quick' implies a convenience/first-look tool rather than the full report path, but the description never states when to prefer it over ga_run_report, ga_realtime, or ga_get_metadata, nor any prerequisites such as obtaining a propertyId. Usage is only implied.

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