Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

zones_create

Create a new Google Tag Manager zone by supplying account, container, and workspace IDs plus the zone resource as JSON, with write operations confirmed before execution.

Instructions

[WRITE] Create a new GTM zone. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. Pass the full resource as a JSON string in bodyJson.

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>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "zones_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull zones resource as a JSON string (e.g. {"name":"...","type":"..."}).
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.

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 / workspaceId / 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?

With no annotations, the description carries the burden and does disclose the write gating: an environment flag plus an explicit confirm flag. It doesn't cover failure modes (duplicate name, permission errors) or what the response contains, but the safety-relevant behavior is well surfaced.

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, front-loaded with the write marker and the action, then preconditions, then the payload format. Nothing is redundant or buried, and the ordering matches how an agent would need the information.

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 5-required-parameter write tool with no output schema, the description covers the action, the gating conditions, and the payload shape. What is missing is modest: no note on required fields inside bodyJson or on error behavior.

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 100%, so all five parameters are already documented, including confirm and bodyJson. The description reinforces the confirm requirement and the JSON-string shape of bodyJson but adds little meaning beyond the schema, so baseline 3 applies.

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 leads with a bracketed [WRITE] marker and a specific verb+resource ('Create a new GTM zone'), which cleanly separates it from the read siblings (zones_get, zones_list) and the mutation siblings (zones_update, zones_delete, zones_revert). An agent can identify the operation without opening the schema.

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 hard preconditions (GTM_MCP_ENABLE_WRITES=true and confirm=true) that gate invocation, which is real usage guidance. It stops short of saying when to create vs. update, or what happens if the zone already exists, so the when-versus-alternatives guidance is only implied.

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