Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

folders_move_entities

Move GTM tags, triggers, and variables into a destination folder; requires write access enabled and per-call confirmation.

Instructions

[WRITE] Move tags/triggers/variables into a folder. 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>",
      "workspaceId": "<workspaceId>",
      "folderId": "<folderId>",
      "confirm": "<confirm>"
    },
    "name": "folders_move_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdNoTag IDs to move.
confirmYes
folderIdYesThe destination folder ID.
accountIdYes
triggerIdNoTrigger IDs to move.
variableIdNoVariable IDs to move.
containerIdYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / folderId / 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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the [WRITE] classification and the two gating requirements (env flag and confirm), which is genuinely useful beyond structured data. However, it does not state the effects of the move — whether entities are removed from any prior folder, whether a tag can belong to multiple folders, or whether the operation is idempotent or reversible.

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 filler, with the write classification and the primary action front-loaded before the gating constraints. Nothing could be removed without losing information.

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 an 8-parameter, 5-required mutation tool with no annotations and no output schema, the description covers gating but omits move semantics, what the call returns, and the role of the three container-scoping IDs. It is adequate to attempt a call but not complete enough to predict its effect.

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 50%: the three entity-ID arrays and folderId are self-documented in the schema and merely restated by the description, while accountId, containerId, workspaceId, and confirm are undocumented in both places. The description adds no syntax, cardinality, or confirm-semantics detail to compensate for that gap.

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?

"[WRITE] Move tags/triggers/variables into a folder" gives a specific verb (move), a specific destination resource (folder), and enumerates the three entity types affected. It is clearly distinguishable from folders_entities (which reads folder membership) and folders_create/update, though it does not name any sibling explicitly.

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 description states prerequisites (GTM_MCP_ENABLE_WRITES=true, confirm=true) which implies this is the mutation path, but it gives no when-to-use vs when-not guidance and never points to folders_entities for inspecting current membership or to a sibling for other move operations. Usage context is inferable rather than stated.

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