Google Analytics 4 MCP Server

Overview Schema Source Related Servers Discussions Admin

get_tracking_snippet

Generate the gtag.js HTML tracking snippet to add Google Analytics 4 tracking to your website. Paste the output directly into your site's HTML.

Instructions

Generate the gtag.js HTML tracking snippet ready to paste into your website.

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": {
      "measurement_id": "<measurement_id>"
    },
    "name": "get_tracking_snippet"
  }
}

Input Schema

Name	Required	Description	Default
`measurement_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description implies a no-side-effect read operation (generating HTML), but with no annotations, it should explicitly state that no data is modified and what the output format is. Lacks detail on authentication or rate limits.

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?

Extremely concise single sentence with no wasted words. Could include a brief parameter hint without becoming verbose.

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?

Given low complexity (1 param, output schema exists), the description is minimally adequate but fails to cover parameter semantics or output expectations, relying on the output schema which is not shown.

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 0%, and the description does not explain the 'measurement_id' parameter (e.g., how to obtain it, its format). The schema only defines it as a required string, leaving the agent without context.

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 ('Generate') and resource ('gtag.js HTML tracking snippet'), clearly distinguishing it from sibling tools that manage accounts, properties, or reports.

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

Usage Guidelines2/5

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

No guidance on when to use or not use this tool, nor any alternatives mentioned. Since no sibling tool does snippet generation, explicit usage context would still be helpful.

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