Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_expanded_data_set

Deletes a GA4 360 expanded data set by its resource name after explicit confirmation, requiring deletes to be enabled. Use it to remove expanded data sets you no longer need.

Instructions

[GA4 DELETE] Delete an expanded data set (360). 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_expanded_data_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the expanded data set to target: "properties/{property}/expandedDataSets/{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 expanded data set to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the expanded data set to target: \"properties/{property}/expandedDataSets/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/expandedDataSets\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose that this is destructive and double-gated by an environment flag plus a confirm parameter. It omits irreversibility, side effects on dependent resources, and error behavior, which matter for a delete operation.

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?

Two compact clauses, front-loaded with the action and resource, then the gating requirements. Nothing is redundant or padded.

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 delete with a fully described schema and no output schema, the description covers action, scope, and invocation prerequisites adequately. The main gap is the absence of consequence detail (irreversibility, affected data) expected when no annotations exist.

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 coverage is 100%, and the schema already documents both `name` (with the full resource-name pattern) and `confirm`. The description only restates that confirm must be true, adding no new meaning beyond the schema.

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 (Delete) and resource (expanded data set, 360) with a [GA4 DELETE] tag that separates it from the create/update expanded-data-set siblings. It stops short of naming alternatives, but the action and target are unambiguous.

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?

Gives real preconditions for invocation (GA4_MCP_ENABLE_DELETES=true and confirm=true), which is useful gating context. It does not say when an agent should choose this over other deletion tools or when deletion is inappropriate, so usage is implied rather than guided.

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