Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

gtag_config_delete

Deletes a GTM gtag config from a workspace, requiring the delete flag enabled and an explicit confirm to prevent accidental removal.

Instructions

[DELETE] Delete a GTM gtag config. 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>",
      "gtagConfigId": "<gtagConfigId>",
      "confirm": "<confirm>"
    },
    "name": "gtag_config_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this delete operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.
gtagConfigIdYesThe gtag configs ID to delete.

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 / gtagConfigId / 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

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description does carry real behavioral weight by disclosing the environment-flag gate and the confirm requirement, both of which change how an agent must prepare the call. It stops short of stating that the deletion is irreversible or what happens to the config's downstream references, which are the remaining facts for a destructive operation.

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 and the gating requirements front-loaded so an agent can decide and prepare the call in a single read. No filler.

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 fully-required, irreversible mutation with zero annotation coverage, the description covers the access gate but not the consequences of the operation (permanence, scope of what is removed). There is no output schema to hint at the result, so the agent is left inferring the aftermath.

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 with patterns and descriptions. The description only echoes the confirm=true constraint and adds no new semantics beyond that baseline.

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?

The description names a specific verb and resource ("Delete a GTM gtag config") and the [DELETE] prefix immediately separates it from the create/get/list/update siblings sharing the gtag_config prefix.

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 the two preconditions that gate invocation (GTM_MCP_ENABLE_DELETES=true and confirm=true), which is clear context an agent needs before calling. It doesn't explicitly name an alternative (e.g., update for reversible tweaks), but for a delete tool the usage condition is unambiguous.

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