Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

containers_create

Create a new Google Tag Manager container by providing account ID, name, and usage context; set confirm to true to execute this write operation.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
nameYesContainer name.
notesNoOptional notes.
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
domainNameNoAssociated domain names.
usageContextYesUsage context(s) for the container.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
  2. 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 supplied, the description carries the full burden and delivers the two most important facts for a mutation tool: the operation is a write, and it is gated behind an environment flag plus an explicit confirm=true parameter. It does not describe failure behavior, side effects, or whether creation is idempotent, which keeps it short of 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?

Two short sentences, zero waste, with the write marker and required preconditions front-loaded. Nothing in the text could be removed without losing 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?

All six parameters are schema-documented for a required-parameter-heavy mutation tool, and the description supplies the operational prerequisites the schema cannot express. The gap is minor: it never indicates what is returned on success (e.g., the new container ID) or what happens when the write gate is disabled, and no output schema exists to cover that.

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 every parameter including the confirm flag is already documented in the schema; the description only echoes the confirm=true requirement. Baseline 3 applies when the schema already does the heavy lifting and the description adds no format or constraint detail beyond it.

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?

States a specific verb and resource ("Create a new GTM container") with a [WRITE] marker that separates it from read-oriented siblings like containers_get, containers_list, and containers_lookup. 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?

The gating conditions (GTM_MCP_ENABLE_WRITES=true and confirm=true) tell the agent when the call will succeed, which is real usage guidance. However, no alternatives are named and there is no explicit statement about when to create a new container versus using containers_get or containers_list to check for an existing one first.

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