Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_channel_group

Deletes a GA4 custom channel group by resource name, requiring explicit confirmation and delete access to prevent accidental removal.

Instructions

[GA4 DELETE] Delete a custom channel group. 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_channel_group"
  }
}

Input Schema

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

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses two behavioral gates (GA4_MCP_ENABLE_DELETES=true and confirm=true), which is real value, but omits whether deletion is permanent, what happens to attached reporting data, or what error is returned when deletes are disabled.

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?

Two short sentences, front-loaded with the action and followed immediately by the safety prerequisites. The "[GA4 DELETE]" prefix is mildly redundant with the tool name but aids scanning.

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

Completeness3/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 no output schema or annotations, the description covers the action and gating requirements adequately. It is still thin on consequences of deletion and dependency warnings, which matter for a permanent delete operation.

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%, with the `name` pattern and `confirm` semantics documented in the schema itself. The description's mention of confirm=true largely restates the schema and adds no format or side-effect detail beyond it.

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?

Description states a specific verb and resource: "Delete a custom channel group." This clearly separates it from the create/update channel-group siblings, though it does not name those alternatives explicitly.

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 by the verb and the GA4 DELETE tag, and the prerequisite environment flag is stated. There is no explicit guidance on when deletion is appropriate versus updating or recreating a group, nor any caution about irreversibility.

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