ga4_list_data_streamsLists all data streams for a GA4 property, including web stream measurement IDs and URLs, so you can identify and manage tracking configurations.
Lists the data streams of a property (web streams with measurement ID G-XXXX and URL).
| Name | Required | Description | Default |
|---|---|---|---|
| property | Yes | GA4 property ID, e.g. '123456789' or 'properties/123456789' |
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing what comes back: web streams with a measurement ID (G-XXXX) and URL, which helps an agent know the output shape. However, it says nothing about other stream types (iOS/Android), pagination, or error behavior when a property lacks streams.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words and the useful output detail placed in parentheses. It is efficient, though slightly thin for a tool an agent may confuse with related GA4 admin listings.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool with annotations covering safety, the description is adequate but not complete: there is no output schema, so the description should say more about what is returned (all stream types, pagination, or the response envelope). It mentions web streams and measurement IDs but leaves open whether non-web streams appear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single 'property' parameter already documents both accepted formats ('123456789' or 'properties/123456789') with an example. The description adds no extra meaning about the parameter, so the baseline 3 applies since the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ('Lists the data streams of a property') and clarifies the scope as belonging to a property. It distinguishes itself reasonably from ga4_list_properties by naming data streams rather than properties, but it never explicitly contrasts with the closest sibling, leaving some ambiguity for an agent choosing between GA4 admin list operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as ga4_list_properties or ga4_get_metadata, nor any stated prerequisites like needing admin access or a resolved property ID first. The only implied usage is that you call it to see streams for a property, which an agent could infer from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.