Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

variables_delete

Permanently delete a Google Tag Manager variable by account, container, workspace, and variable ID, with explicit confirmation required to prevent accidental removal.

Instructions

[DELETE] Delete a GTM variable. 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>",
      "variableId": "<variableId>",
      "confirm": "<confirm>"
    },
    "name": "variables_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
variableIdYes
containerIdYes
workspaceIdYes

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 / variableId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does the important part by flagging the operation as destructive and gated behind a feature flag plus an explicit confirm argument, but it omits whether the deletion is permanent or revertible in a GTM workspace, and what scope of impact it has.

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 tight sentences with the destructive marker and the resource front-loaded, then the gating requirements. No filler or repetition.

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 destructive five-parameter tool with no annotations and no output schema, the definition covers the safety gate and the confirm flag but leaves the identity parameters and the reversibility/scope of deletion unexplained. Adequate to avoid a blind call, not complete enough for confident use.

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 five required parameters, so the description must compensate and largely does not. It explains only confirm=true, leaving accountId, containerId, workspaceId, and variableId entirely undocumented beyond their numeric-string patterns.

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 plus resource ('Delete a GTM variable') and the bracketed [DELETE] prefix makes the operation unmistakable. An agent can distinguish it from variables_create, variables_update, and variables_list without further reading, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives concrete preconditions for invoking it: the GTM_MCP_ENABLE_DELETES environment flag must be true and confirm must be set to true. That is actionable context, but it never says when to prefer this over alternatives such as variables_update or revert, and it lists no exclusions.

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