Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

transformations_delete

Deletes a GTM transformation from a workspace. Requires deletes enabled and confirm=true to prevent accidental removal.

Instructions

[DELETE] Delete a GTM transformation. Requires GTM_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": {
      "accountId": "<accountId>",
      "containerId": "<containerId>",
      "workspaceId": "<workspaceId>",
      "transformationId": "<transformationId>",
      "confirm": "<confirm>"
    },
    "name": "transformations_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this delete operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.
transformationIdYesThe transformations ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / containerId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / transformationId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.5/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 behavioral burden. It usefully discloses the environment-variable gate and the confirm flag, which an agent needs before invoking. It stops short of saying whether the deletion is permanent, whether it affects the live container or only a workspace, and whether a subsequent publish is needed — material facts for a destructive 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?

Three short clauses, operation type front-loaded in brackets, then action, then prerequisites. Nothing extraneous and no filler.

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 five-parameter destructive tool with no annotations and no output schema, the definition covers the gating requirements but not the consequences of the call. Without any annotation declaring destructiveness, the description should more fully explain irreversibility and scope of effect.

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 all five parameters are already documented in the schema. The only parameter-related statement in the description — that confirm must be true — duplicates the schema's own 'Must be true to confirm this delete operation.' Baseline 3 applies since the schema does the work.

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 and resource: 'Delete a GTM transformation.' The [DELETE] prefix reinforces the operation type, and the 'GTM transformation' scope distinguishes it from the sibling delete tools for tags, triggers, templates, clients, etc. It doesn't name a specific sibling alternative, but the resource scoping is 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 hard prerequisites (GTM_MCP_ENABLE_DELETES=true and confirm=true) which is genuine when-to-use guidance. However, it never addresses when to delete versus transformations_revert or transformations_update, nor any warning about when not to use it.

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