google-tag-manager-mcp

Gtm Folder

gtm_folder

Manage Google Tag Manager folders: create, read, update, delete, or revert them. List folder entities and move tags, triggers, or variables into folders with confirmation.

Instructions

Manage GTM folders.

Standard CRUD+revert like gtm_tag, plus:

entities: path="/folders/{id}" → list entities in folder. (read-only)
move_entities_to_folder: path="/folders/{id}", params={tagId/triggerId/variableId}, confirm=true. Moves entities into the folder. (destructive)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`action`	Yes
`config`	No
`params`	No
`parent`	No
`confirm`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It explicitly notes that 'entities' is read-only and 'move_entities_to_folder' is destructive and requires confirm=true. However, it does not disclose the safety profile of the standard CRUD operations (e.g., delete, revert) or mention any side effects, permissions, or irreversible changes beyond the one noted. The description provides some transparency but not enough for a tool with multiple destructive operations.

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 description is concise, with a one-line summary and a clear bullet list for the special actions. It is front-loaded and avoids unnecessary verbosity. The structure is scannable and helps the agent quickly identify key operations.

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?

Given the tool's complexity (6 parameters, multiple actions, no annotations, 0% schema coverage), the description is incomplete. It fails to specify the full set of action names, explain the general CRUD behavior, or define the 'config' and 'parent' parameters. While an output schema exists, it doesn't cover input semantics. The description is not sufficient for an agent to correctly call this tool without additional 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%, so the description must compensate. It provides path and params hints for the two special actions (entities and move_entities_to_folder), but it does not explain the 'action' parameter values (e.g., create, read, update, delete, revert), nor the meaning of 'config' and 'parent'. The description adds minimal value for the general CRUD flow, leaving the agent to guess parameter usage.

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 clearly states the tool manages GTM folders and enumerates the operations (standard CRUD+revert plus two specific actions). It references gtm_tag as a baseline, which distinguishes it from other sibling tools. However, it relies on the agent knowing what 'standard CRUD+revert' entails, so it's not fully self-contained.

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 implies usage by comparing to gtm_tag and adding folder-specific actions, but it does not explicitly state when to use this tool over alternatives or when not to use it. It also doesn't mention exclusions or specific scenarios that would route to a different tool. The 'like gtm_tag' hint gives some context, but it's not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server