Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

environments_create

Creates a new Google Tag Manager environment in a container, letting you define a name, description, and default preview URL for staging or testing traffic.

Instructions

[WRITE] Create a new GTM environment. 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>",
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "environments_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoDefault preview page URL for the environment.
nameYesEnvironment name.
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
descriptionNoEnvironment description.
enableDebugNoWhether to enable debug by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does usefully disclose the two flags that must be set for the write to succeed, which an agent would otherwise have to discover by failure, but it says nothing about permissions, duplicate-name behavior, or side effects of creating an environment.

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, front-loaded with the write tag and the action, followed by the gating requirement. Nothing is redundant or padded.

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 7-parameter creation tool with a fully documented schema and no output schema, the definition covers the action and the non-obvious write gating. What remains thin is failure/duplicate handling, which is a modest gap rather than a blocking one.

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% for all 7 parameters including confirm, so the schema already documents every field. The description repeats confirm=true but adds no meaning about accountId/containerId scoping or defaults beyond what the schema states; baseline 3 applies.

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: 'Create a new GTM environment', with a [WRITE] prefix that distinguishes it from read siblings like environments_get and environments_list. It does not explicitly contrast with environments_update, but the create/update distinction is inferable from the verb.

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?

No explicit when-to-use versus alternatives is given. The description instead supplies prerequisites for invocation (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is useful but is gating guidance rather than selection guidance.

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