Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_delete

Deletes a specific Google Tag Manager container version after delete-flag opt-in and confirmation, while blocking deletion of currently published live versions.

Instructions

[DELETE] Delete a GTM container version. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true. Cannot delete a currently published (live) version.

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>",
      "containerVersionId": "<containerVersionId>",
      "confirm": "<confirm>"
    },
    "name": "versions_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
containerIdYes
containerVersionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / containerVersionId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two non-obvious behavioral facts: a server-side feature flag gate and a hard restriction on deleting the live version. It does not say whether the delete is reversible (a versions_undelete sibling implies soft delete) or what happens to dependent entities, so the irreversibility question stays open.

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 sentences, front-loaded with the [DELETE] operation tag and the riskiest constraint surfaced before the details. No filler and nothing buried.

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?

There is no output schema and no annotations, so the description is the only source of safety and side-effect information. It covers gating and the live-version block, but leaves undo-ability and post-delete state of the container version undocumented for a destructive 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 description coverage is 0% across four required parameters, yet the description only adds meaning for `confirm` (must be true). accountId, containerId, and containerVersionId are self-naming and pattern-constrained to digits in the schema, so the residual gap is modest, but nothing clarifies format, hierarchy, or whether containerVersionId is numeric or opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

'[DELETE] Delete a GTM container version' gives an unambiguous verb plus resource, and the tags make it trivially distinguishable from versions_publish, versions_get, or versions_undelete. An agent can select this tool without opening the schema.

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?

It states concrete preconditions (GTM_MCP_ENABLE_DELETES=true and confirm=true) and one explicit exclusion (live/published versions cannot be deleted). What's missing is routing to the obvious alternative for that excluded case — versions_undelete or unpublish-then-delete — which is left to inference.

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