Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

built_in_variables_disable

Disable one or more built-in variables in a GTM workspace to remove unused variables from the workspace; requires delete-enabled configuration and explicit confirmation.

Instructions

[DELETE] Disable one or more built-in variables in a GTM workspace. 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>",
      "types": "<types>",
      "confirm": "<confirm>"
    },
    "name": "built_in_variables_disable"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesYesArray of built-in variable types to disable.
confirmYes
accountIdYes
containerIdYes
workspaceIdYes

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

TDQS

A3.6/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 burden. It does valuable work by disclosing this is a destructive-class operation gated behind an env flag and a confirm flag, but it omits whether the change is reversible, whether it affects only the workspace draft or published versions, and what happens to dependent tags.

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, front-loaded with the destructive-operation marker and followed immediately by the invocation prerequisites. Nothing is wasted and the critical gating information appears before any detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter destructive mutation with no annotations and no output schema, the definition covers the operational essentials: what it does, what it touches, and what flags are needed to call it. It falls short only on reversibility and scope-of-effect, which matter for a delete-class action.

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 coverage is only 20%, so the description must compensate, and it partially does: 'one or more' explains that types is an array, and 'confirm=true' gives the expected value for confirm. accountId, containerId, and workspaceId remain undocumented beyond self-describing names and digit patterns, leaving a real gap.

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 ('Disable one or more built-in variables') plus its scope ('in a GTM workspace'), which cleanly distinguishes it from the enable/list siblings in the tool name itself. The '[DELETE]' prefix adds a class signal, though the description never explicitly contrasts it with built_in_variables_enable or built_in_variables_revert.

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 communicates prerequisites well: GTM_MCP_ENABLE_DELETES=true and confirm=true are required, which tells the agent how to invoke successfully. It gives no guidance on when to prefer this over built_in_variables_revert or variables_delete, nor any exclusions, so usage is only implied.

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