Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

triggers_delete

Deletes a Google Tag Manager trigger after explicit confirmation (confirm=true), gated by the GTM_MCP_ENABLE_DELETES flag.

Instructions

[DELETE] Delete a GTM trigger. 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>",
      "triggerId": "<triggerId>",
      "confirm": "<confirm>"
    },
    "name": "triggers_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
triggerIdYes
containerIdYes
workspaceIdYes

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

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it does disclose that this is a gated destructive operation requiring an environment flag plus an explicit confirm boolean, which is valuable. It stops short of stating whether deletion is permanent or reversible, what happens to tags/other entities referencing the trigger, 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 operation tag front-loaded and the gating requirements immediately after. Nothing is wasted or buried.

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

Completeness2/5

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

For a destructive tool with no annotations, no output schema, and five required parameters at zero description coverage, the definition is under-specified. An agent still lacks the irreversibility profile and the meaning of four of the five identifiers, which matter for calling a delete correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters, so the description must compensate and largely does not. It clarifies that confirm must be true but says nothing about the accountId/containerId/workspaceId/triggerId path semantics or the numeric-only pattern constraints.

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 pairs a specific verb with a specific resource ("Delete a GTM trigger"), and the [DELETE] prefix makes the operation class unambiguous. It does not explicitly name sibling alternatives, but the create/get/list/update siblings are cleanly separated by verb alone.

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 states two concrete preconditions for use (GTM_MCP_ENABLE_DELETES=true and confirm=true), which is real actionable guidance. However, it gives no when-to-use versus when-not guidance, no mention of checking the trigger first (e.g. via triggers_get), and no note that the delete occurs within a specific workspace.

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