gtm-mcp-server

Overview Schema Source Related Servers Discussions Admin

gtm_create_trigger

Create a Google Tag Manager trigger in a chosen workspace draft. Specify trigger type and name to track events such as pageviews, clicks, or custom events.

Instructions

Create a trigger in an explicitly selected workspace draft.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Display name of the trigger.
`type`	Yes	GTM trigger type, e.g. 'pageview', 'domReady', 'click', 'linkClick', 'customEvent', or 'timer'.
`limit`	No
`notes`	No
`filter`	No	Filter conditions in GTM API format.
`account`	Yes	Name or ID of the GTM account (e.g. 'My Company' or '1234567').
`interval`	No
`selector`	No
`container`	Yes	Name, GTM container ID (publicId, e.g. GTM-XXXX), or internal container ID.
`eventName`	No
`parameter`	No
`workspace`	Yes	Workspace name or ID. Required for every mutating operation.
`waitForTags`	No
`parentFolderId`	No
`autoEventFilter`	No
`checkValidation`	No
`intervalSeconds`	No
`uniqueTriggerId`	No
`customEventFilter`	No
`visibilitySelector`	No
`waitForTagsTimeout`	No
`visiblePercentageMax`	No
`visiblePercentageMin`	No
`maxTimerLengthSeconds`	No
`totalTimeMinMilliseconds`	No
`verticalScrollPercentageList`	No
`continuousTimeMinMilliseconds`	No
`horizontalScrollPercentageList`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 29, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds one genuinely useful behavioral fact: the write lands in a draft workspace rather than live configuration. It says nothing about permissions, validation behavior, or what a failed create does.

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?

A single front-loaded sentence with no filler words. It is efficient, though the brevity borders on under-specification for a 28-parameter mutation tool rather than being a model of tight structuring.

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 28-parameter creation tool with 21% schema coverage, the description is drastically incomplete — no guidance on trigger-type-dependent fields, filter formats, or draft/workspace lifecycle. An output schema exists so return values needn't be covered, but that does not excuse the missing parameter and workflow 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 only 21% across 28 parameters, so the description must compensate and it contributes zero parameter meaning. Even limit, filter, parameter, customEventFilter and the trigger-type-specific fields described only by unhelpful $refs are left unexplained.

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 ('Create a trigger') plus a scoping constraint ('in an explicitly selected workspace draft'), which lets an agent tell it apart from gtm_create_tag or gtm_create_variable. It stops short of any differentiation from the closely related trigger siblings (update/delete/revert).

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 phrase 'explicitly selected workspace draft' implies a prerequisite — a workspace must already be chosen before calling — but the description never states when to use this versus gtm_create_trigger alternatives or what happens if no workspace is set. Usage is implied rather than specified.

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