Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

templates_delete

Deletes a Google Tag Manager template from a specified account, container, and workspace after explicit confirmation to prevent accidental removal.

Instructions

[DELETE] Delete a GTM template. 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>",
      "templateId": "<templateId>",
      "confirm": "<confirm>"
    },
    "name": "templates_delete"
  }
}

Input Schema

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

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 / templateId / 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 provided, so the description carries the full burden; it does disclose that this is a gated, double-confirmed destructive operation via the env flag and confirm parameter, which is meaningful behavioral context. It does not say whether the deletion is permanent or only affects the workspace, what happens to entities referencing the template, or whether a publish step is needed for the change to take effect.

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 short sentences with the destructive nature front-loaded and the prerequisites immediately after. Nothing is wasted and an agent can parse the requirements in one pass.

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?

With five required parameters, no annotations and no output schema, the definition covers the safety gates but not the consequences: irreversibility, effect on the workspace vs. container, and error behavior when the env flag is unset are all unstated. It is minimally sufficient but thin for a destructive tool with zero annotation coverage.

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 every parameter including confirm, accountId, containerId, workspaceId and templateId is already documented in the schema. The description only restates confirm=true, adding no syntax, format, or nesting meaning beyond the structured fields; baseline 3 applies.

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?

The description states a specific verb and resource ("Delete a GTM template"), which is enough to separate it from templates_get, templates_update and the other templates_* siblings. It loses a point because the "[DELETE]" tag merely repeats the verb rather than adding scope detail, and it does not mention what kind of template (e.g. custom vs. gallery-imported) is affected.

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?

It gives invocation preconditions (GTM_MCP_ENABLE_DELETES=true and confirm=true), which is real guidance for actually calling the tool. However, it gives no when-to-use-vs-alternative guidance, such as when to use templates_revert instead of a hard delete, and no statement of what state the template must be in first.

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