Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

folders_create

Creates a Google Tag Manager folder in a specified account, container, and workspace, requiring write access enabled and confirm=true to proceed.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
nameYes
notesNo
confirmYes
accountIdYes
containerIdYes
workspaceIdYes

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

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the most important operational trait: this is a gated write that fails unless the environment flag is enabled and confirm is true. It does not disclose side effects such as whether the new folder is immediately visible, whether a workspace sync/publish is needed, or what happens on name collision.

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 tight sentences with the write marker front-loaded and the gating requirements immediately after. Nothing is wasted and the most decision-relevant information appears first.

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

Completeness2/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, no output schema, and no parameter documentation, the definition is thin: it explains the access gate but not the resource identifiers required to target the correct account/container/workspace. An agent could satisfy the gate and still call the tool with invalid hierarchy context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely does not. Only confirm is explained (must be true), while name, notes, accountId, containerId, and workspaceId receive no semantic explanation, format hints, or uniqueness constraints beyond their regex patterns.

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?

The description gives a specific verb and resource ("Create a GTM folder"), which is unambiguous and clearly distinct from siblings like folders_update, folders_delete, and folders_list. It stops short of explicitly naming those alternatives, so it lands just under a 5.

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 [WRITE] tag plus the two prerequisites (GTM_MCP_ENABLE_WRITES=true and confirm=true) tell the agent the conditions under which this call will succeed. However, there is no guidance on when to choose create versus folders_update or folders_move_entities, and no note on required hierarchy context such as whether the workspace must already exist.

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