Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

folders_update

Updates a Google Tag Manager folder with read-modify-write, keeping omitted fields unchanged; requires writes enabled and confirm=true.

Instructions

[WRITE] Update a GTM folder (read-modify-write: omitted fields are preserved). 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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
notesNo
confirmYes
folderIdYes
accountIdYes
containerIdYes
fingerprintNo
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. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does meaningful work: it declares the write gating flag, the confirm requirement, and the read-modify-write contract where omitted fields are preserved. It omits error/rollback behavior and permission scope, which keeps it from 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?

A single front-loaded sentence with the write tag first, the mutation semantics parenthesized, and the gating requirements last. No filler.

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 mutation tool with no annotations, no output schema, and 8 undocumented parameters, the description covers the highest-risk concerns (write gating, partial update semantics) but leaves the identifier and fingerprint parameters opaque. An agent could invoke it but not confidently supply fingerprint or predict failure modes.

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 8 parameters, and the description only explains confirm and the partial-update behavior of name/notes. The five required identifier parameters (accountId, containerId, workspaceId, folderId) and especially fingerprint — an unusual field likely tied to concurrency — are left entirely unexplained in both schema and description.

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 ("Update a GTM folder") and tags it "[WRITE]", so the agent can separate it from folders_get, folders_list, folders_create and folders_delete by intent. It stops short of naming any sibling explicitly, but the mutation intent 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?

The description gives preconditions for calling it (GTM_MCP_ENABLE_WRITES=true and confirm=true) but never says when to choose update over create/delete or what happens if the folder ID does not exist. Usage is implied by the verb rather than guided.

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