Skip to main content
Glama
Sign In
Google Analytics 4 MCP Server

Google Analytics 4 MCP Server

by stucchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_web_data_stream

Create a web data stream for a GA4 property and obtain the Measurement ID (G-XXXXX) by specifying the property ID and default URL.

Instructions

Create a web data stream and get the Measurement ID (G-XXXXX).

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

Input Schema

NameRequiredDescriptionDefault
default_uriYes
property_idYes
display_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description must disclose side effects and safety. It only mentions creating and getting an ID, with no details on permissions, irreversibility, quotas, or other behavioral impacts.

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, clear sentence that efficiently conveys the core action and primary output.

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?

Given 3 parameters (2 required) and an output schema, the description is too minimal. It omits details on what a web data stream is, validation constraints (e.g., URI format), and the purpose of the Measurement ID.

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

Parameters1/5

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

Schema description coverage is 0%, but the description adds no meaning to the parameters (default_uri, property_id, display_name). It does not clarify formats, allowed patterns, or relationship to the Measurement ID.

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 clearly states the action ('create a web data stream') and the key output ('get the Measurement ID'), distinguishing it from sibling tools like 'create_property'.

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 this tool vs alternatives (e.g., list_data_streams or create_property). No prerequisites or context provided, such as needing an existing property.

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

Deploy Server

Other Tools