AdCopilot

GA4: create data stream

ga4_create_data_stream

Create a data stream on a GA4 property. It adds one data stream and changes nothing existing; the stream collects nothing until its tag is on the website or app.

Tools revision: d80f65c0.

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": "<property>",
      "display_name": "<display_name>"
    },
    "name": "ga4_create_data_stream"
  }
}

Input Schema

Name	Required	Default
`property`	Yes
`stream_type`	No	WEB_DATA_STREAM
`display_name`	Yes
`web_stream_data`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior. The description usefully adds that only one stream is added, that nothing existing is modified, and that the stream collects no data until its tag is deployed on the site or app — real context about the tool's effect and its 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?

The first three sentences are front-loaded and earn their place. The trailing 'Tools revision: d80f65c0.' is internal metadata that adds nothing for an agent choosing or invoking the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. The only meaningful gap is parameter-level detail, which is scored separately; overall the description is sufficient for a create-one-resource tool.

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% across four parameters. The description only hints that 'property' identifies the GA4 property and never explains display_name or the critical stream_type choice (WEB_DATA_STREAM vs. app streams) or what web_stream_data expects, so it fails to compensate for the schema gap.

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 states a specific verb and resource ('Create a data stream on a GA4 property'), which is enough for an agent to know exactly what is being created. It does not explicitly contrast itself with ga4_update_data_stream or ga4_list_data_streams, relying on the name and sibling set to make the distinction.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the reader infers 'use this when you need a new stream' from the create verb. There is no explicit when-not guidance (e.g., use ga4_update_data_stream instead to modify an existing stream), so the agent must reason from sibling names.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?