Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

zones_delete

Permanently removes a Google Tag Manager zone from a workspace when deletes are enabled and confirmation is supplied. Use it to clean up unused or misconfigured zones by account, container, and zone ID.

Instructions

[DELETE] Delete a GTM zone. 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>",
      "zoneId": "<zoneId>",
      "confirm": "<confirm>"
    },
    "name": "zones_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYesThe zones ID to delete.
confirmYesMust be true to confirm this delete operation.
accountIdYesThe GTM account ID.
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 / workspaceId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / zoneId / 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 does add real value by disclosing the environment-flag gate and the confirmation requirement, but it omits the consequences: whether the delete is permanent, whether it applies to the workspace or published container version, and whether a publish is needed 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 terse sentences, front-loaded with the destructive marker and the action, followed by the invocation preconditions. Nothing is wasted.

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 gating requirements but leaves out irreversibility, scope of effect (workspace vs. live container), and error behavior when the flag is disabled. Adequate but with clear gaps.

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 including confirm are already documented in the schema. The description only restates confirm=true and adds no semantics about zoneId, accountId, containerId or workspaceId beyond what the schema provides; 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?

States a specific verb and resource ("Delete a GTM zone") and the [DELETE] tag plus the zones_* naming makes it distinguishable from zones_create, zones_get, zones_update and zones_revert. It stops short of explicitly contrasting with zones_revert, which is the nearest ambiguous sibling.

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 prerequisites for invocation (GTM_MCP_ENABLE_DELETES=true and confirm=true) but no when-to-use guidance, no mention of alternatives such as reverting a workspace change, and no note on when deletion is inappropriate.

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