Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_data_stream

Deletes a GA4 data stream by resource name, removing its measurement ID or Firebase app ID. Requires deletes enabled and confirm=true.

Instructions

[GA4 DELETE] Delete a data stream (removes its measurement ID / firebase app id). Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.

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": {
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "ga4_delete_data_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the data stream to target: "properties/{property}/dataStreams/{id}".
confirmYesMust be true to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the data stream to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the data stream to target: \"properties/{property}/dataStreams/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/dataStreams\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does reasonably well: it declares the operation is destructive, names exactly what is removed (measurement ID / firebase app id), and discloses the two gates that must be satisfied before the call will succeed. It does not state irreversibility or any downstream effects on collected data, which keeps it from a 5.

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?

A single dense sentence with the destructive tag front-loaded and the consequence placed before the prerequisites. Every clause carries information; the bracketed '[GA4 DELETE]' prefix is mildly redundant with the tool name but aids scanning among many siblings.

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 two-parameter destructive tool with full schema coverage and no output schema, the description covers the essentials: what is deleted, what identifier disappears, and the two conditions required for success. Only irreversibility/rollback expectations are missing.

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?

Schema description coverage is 100%, so both 'name' (with its resource-name pattern) and 'confirm' are already fully documented in the schema. The description only repeats that confirm must be true and adds no syntax or format detail beyond the structured fields, so 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?

The description uses a specific verb and resource ('Delete a data stream') and parenthetically states the concrete consequence ('removes its measurement ID / firebase app id'), so an agent can tell it apart from the many sibling delete tools by resource alone. It stops short of explicitly naming an alternative, which is what a 5 would require.

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?

It gives hard prerequisites ('Requires GA4_MCP_ENABLE_DELETES=true and confirm=true') rather than guidance on when to choose this tool versus alternatives such as ga4_delete_expanded_data_set. Usage is implied by the destructive nature and the flag gate, but no when-not-to-use condition is stated.

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