Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

environments_update

Update an existing Google Tag Manager environment by changing only specified fields; omitted settings are preserved. Requires writes enabled and confirm=true.

Instructions

[WRITE] Update an existing GTM environment (read-modify-write: omitted fields are preserved). Requires GTM_MCP_ENABLE_WRITES=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>",
      "environmentId": "<environmentId>",
      "confirm": "<confirm>"
    },
    "name": "environments_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoNew default preview page URL.
nameNoNew environment name.
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
descriptionNoNew description.
enableDebugNoWhether to enable debug by default.
fingerprintNoCurrent fingerprint (for optimistic locking).
environmentIdYesThe GTM environment ID to update.

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

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden and does well: it declares the operation is a write, explains read-modify-write semantics (omitted fields preserved), and states both gating requirements. It omits what happens on fingerprint/optimistic-locking conflict and what the response contains, which are the main remaining behavioral gaps.

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?

A single sentence with the write marker front-loaded, the key behavioral semantic in a parenthetical, and the two prerequisites at the end. No filler and nothing an agent must read past to get the gating conditions.

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 no annotations, no output schema and nine parameters, the description covers the essentials: write classification, partial-update semantics, and the two invocation gates. The remaining shortfall is conflict/fingerprint failure behavior and any note on permissions or irreversibility of overwritten values.

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 nine parameters including confirm, fingerprint and the ID patterns are already documented in the schema, establishing the baseline of 3. The description adds one genuinely useful semantic point beyond the schema — that omitted fields are preserved — but adds nothing about individual field behavior.

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 and resource ("Update an existing GTM environment") and tags it as a write operation, which cleanly separates it from the environments_create/get/list/delete siblings. It does not explicitly name an alternative, but the action verb alone makes the intent unambiguous.

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 concrete preconditions for use: GTM_MCP_ENABLE_WRITES=true must be set and confirm=true must be supplied, otherwise the call cannot proceed. It stops short of naming when an agent should prefer environments_get first or when to use environments_create instead, so usage is clear but not fully exclusive.

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