Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

containers_combine

Merge a source Google Tag Manager container into a target container, leaving the target as the surviving container; requires write access and confirm=true.

Instructions

[WRITE] Combine (merge) another container into this one. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. ⚠️ This merges the source container identified by containerIdToCombine into the target container.

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>",
      "containerIdToCombine": "<containerIdToCombine>",
      "confirm": "<confirm>"
    },
    "name": "containers_combine"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
containerIdYesThe target container ID (the surviving container).
settingSourceNoWhich container's settings to keep.
containerIdToCombineYesThe container ID to merge into the target.
allowUserPermissionFeatureUpdateNoAllow updating the user-permission feature during combine.

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. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It does disclose that this is a gated write requiring an environment flag plus confirm=true, and the ⚠️ plus 'merges ... into' signals a destructive, absorbing operation. It stops short of saying whether the source container is deleted or becomes unusable, whether the merge is reversible, or what happens to conflicting settings beyond the schema's settingSource enum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The [WRITE] tag and precondition sentence are front-loaded and useful, and the warning marker draws attention to the destructive nature. The third sentence partly restates the first, which is mild redundancy but aids comprehension of direction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no annotations and no output schema, the description covers the write gate, the confirm requirement, and merge direction. It is not complete on consequences: it never states that the source container is consumed or what the agent should expect afterward, which matters most for an irreversible combine.

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 confirm, settingSource, and allowUserPermissionFeatureUpdate is documented in the schema. The description adds only the source-versus-target distinction for containerId/containerIdToCombine, which the schema largely already conveys, so this is the baseline 3.

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?

Uses a specific verb (combine/merge) and resource (container), and the third sentence clarifies the direction: the container identified by containerIdToCombine is merged into the target container. It does not differentiate from nearby siblings such as containers_move_tag_id, but the operation itself is unambiguous.

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 preconditions for use (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is real usage guidance. However, it gives no when-not-to-use guidance or comparison against alternatives, so the agent must infer that this is the heavyweight option versus moves or separate updates.

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