Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_update_entity

Update a Google Tag Manager tag, trigger, or variable after reading the current entity and preserving its fingerprint; requires explicit user confirmation before applying the approved change.

Instructions

Update a GTM tag, trigger, or variable. Read it first and preserve its fingerprint. Requires explicit user confirmation.

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>",
      "entity": "<entity>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_update_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesComplete GTM entity body, including the current fingerprint.
entity_pathYes
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

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world mutation, so the description adds real value by disclosing the read-before-write fingerprint protocol and the confirmation requirement — both are behavioral obligations not visible in the schema. It stops short of explaining what happens on a fingerprint mismatch or whether a workspace must be active, which keeps it from a 5.

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?

Three short sentences with no waste: the action first, then the read/fingerprint prerequisite, then the confirmation gate. Every sentence carries information an agent needs before calling.

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 mutation tool with a nested entity object, no output schema, and four required parameters, the description covers the critical safety path (read, preserve fingerprint, confirm). It omits workspace/version context and error behavior, which are the remaining gaps for a GTM mutation.

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 75%, and the schema already documents entity, change_summary, and user_confirmed in detail. The description's mention of the fingerprint largely restates the schema's 'including the current fingerprint' note, and it says nothing about entity_path. Baseline 3 applies when the schema does the heavy lifting.

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 (Update) and specific resources (GTM tag, trigger, or variable), which is unambiguous against siblings like gtm_create_entity and gtm_delete_entity. It does not explicitly name an alternative tool, but the resource scope is precise enough to distinguish it.

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?

Gives two concrete preconditions: read the entity first and preserve its fingerprint, and obtain explicit user confirmation. It does not spell out when to choose update over delete/create or what to do if the fingerprint has changed, but the usage context is clear.

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