Skip to main content
Glama

Google Analytics setup

analytics_setup
Read-only

Inspect a GA4 property's setup: web streams and measurement IDs, key events, linked Google Ads accounts, and custom dimensions and metrics. Read-only check before proposing changes.

Instructions

How a GA4 property is set up: its web streams with their measurement IDs (what the site's tag must use), which events are key events (GA4's conversions), which Google Ads accounts it's linked to, and its custom dimensions and metrics with the name analytics_report takes. Check this before proposing setup changes. Changes nothing.

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": {
      "property_id": "<property_id>"
    },
    "name": "analytics_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYesGA4 property id, digits only (from analytics_properties)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Changes nothing' while adding useful context about what the returned data is used for (the measurement ID the site tag must use, the dimension names analytics_report takes). Beyond that it does not describe size, pagination, or behavior when a property id is unknown.

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?

Front-loaded with the resource, followed by a compact enumeration and two short closing sentences. The enumerating sentence is long and comma-heavy but every clause carries information an agent needs.

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 no output schema, the description must convey return content and it does so by listing the four setup facets. Minor gaps remain: nothing about how large the payload can get or how missing/unauthorized property ids are handled.

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 the schema already documents property_id as digits-only sourced from analytics_properties. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 names the specific resource (a GA4 property's setup) and enumerates what that setup comprises: web streams and measurement IDs, key events, linked Google Ads accounts, and custom dimensions/metrics. It also distinguishes itself implicitly from analytics_report by explaining the naming convention that tool relies on.

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?

Explicit instruction 'Check this before proposing setup changes' gives a clear trigger and implicitly points at the propose_analytics_changes workflow. It stops short of stating when this tool should not be used or naming alternatives directly.

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