Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_delete_entity

Destructive

Delete a GTM tag, trigger, or variable from a workspace only after explicit confirmation of the exact change to prevent accidental deletions.

Instructions

Delete a GTM tag, trigger, or variable from a workspace. Requires explicit confirmation of this exact deletion.

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": {
      "entity_path": "<entity_path>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_delete_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_pathYes
fingerprintNoCurrent entity fingerprint, recommended for concurrency safety.
change_summaryYesConcise exact change the user approved in the current request.
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds the confirmation-at-action-time requirement, which is useful behavioral context not expressed in the annotations. It does not disclose irreversibility, whether deleting a variable breaks referencing tags, or concurrency behavior implied by the fingerprint parameter.

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 zero filler: the action and scope come first, followed by the confirmation precondition. Nothing could be removed without losing information.

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, non-idempotent mutation the definition covers purpose and the confirmation gate, and annotations plus a well-described schema fill in much of the rest. It is still thin on consequences (permanence, effect on dependent entities) and on entity_path format, which matters for a tool that can destroy production GTM configuration.

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 75%, with change_summary, user_confirmed, and fingerprint all carrying their own descriptions, so the schema does the heavy lifting. The description adds nothing about entity_path formatting (e.g. account/container/workspace path) or the interaction between fingerprint and concurrency safety, leaving the one undocumented parameter unexplained.

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 names a specific verb and resource set ('Delete a GTM tag, trigger, or variable') and scopes it to a workspace, so an agent can tell it apart from gtm_delete_workspace and the create/update/get entity siblings. It stops short of explicitly contrasting those siblings, but the resource enumeration does most of the differentiation work.

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?

The sentence 'Requires explicit confirmation of this exact deletion' establishes a precondition for invocation, which is real usage guidance. However, there is no statement of when to prefer this over alternatives (e.g. deleting a whole workspace) or when not to use it, so the guidance remains implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.