Skip to main content
Glama
Sign In
ga4-mcp-server

ga4-mcp-server

by dienhokhanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

List data streams

list_data_streams
Read-only

Retrieve a GA4 property's web, Android, and iOS data streams with measurement IDs (G-XXXX), website URLs, and app IDs to verify tracking setup.

Instructions

List a property's data streams (web, Android, iOS) including measurement IDs (G-XXXX), website URLs and app IDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_data_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyNoGA4 property: numeric ID ("123456789"), resource name ("properties/123456789") or display name ("My Website"). Defaults to GA4_DEFAULT_PROPERTY if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 and scope are covered structurally. The description adds useful output context by naming the fields returned (measurement IDs, website URLs, app IDs), but says nothing about pagination, result limits, empty-property behavior, or auth needs.

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?

A single front-loaded sentence with zero filler; the resource and the most useful returned fields are stated up front without redundancy.

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?

For a simple one-optional-parameter read tool with annotations covering the safety profile, the description is nearly sufficient, and it usefully previews the returned fields in place of a missing output schema. Only the absence of any routing guidance to sibling list tools keeps it short of complete.

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?

Only one optional parameter exists and schema coverage is 100%, so the schema fully documents the property formats and the GA4_DEFAULT_PROPERTY default. The description restates the property scoping ('a property's data streams') but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (List) and resource (a property's data streams), and even enumerates the stream types (web, Android, iOS) and the key fields returned (measurement IDs like G-XXXX, URLs, app IDs). This distinguishes it from siblings like list_properties or list_accounts by resource, though it never explicitly names those alternatives.

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?

The description says nothing about when to call this versus sibling list tools, nor about prerequisites (e.g., needing a property ID first) or how it relates to get_property. Usage is only inferable from the resource name.

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