Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Tag Manager trigger details

get_gtm_trigger
Read-only

Fetch a GTM trigger's full raw config—filters, validation, and every tag using it—to diagnose why a tag fires or not. Reads live or draft workspace state.

Instructions

Get the full RAW configuration for a single GTM trigger.

Includes filters, auto-event filters, custom-event filters, validation settings, and a list of every tag that uses this trigger. Helps diagnose why a tag with a specific trigger ID does or doesn't fire. An unknown trigger_id returns an error with the available trigger IDs. Reads the live container, or a workspace's unpublished state when workspace_id is set.

Tag Manager API: https://developers.google.com/tag-platform/tag-manager/api/v2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trigger_idYesNumeric GTM trigger ID, as listed by list_gtm_triggers or a tag's firing/blocking triggers.
workspace_idNoWorkspace to read (see list_gtm_workspaces), which includes drafted changes that are not published yet. Empty reads the live (published) container version.
gtm_account_idNoNumeric GTM account ID (see list_gtm_accounts). Empty uses gtm.account_id from the config.
gtm_container_idNoNumeric GTM container ID (see list_gtm_containers). Empty uses gtm.container_id from the config.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.27.1
    • addedInput schema / properties / gtm_account_id / description
      Added value: +"Numeric GTM account ID (see list_gtm_accounts). Empty\nuses gtm.account_id from the config."
    • addedInput schema / properties / gtm_container_id / description
      Added value: +"Numeric GTM container ID (see list_gtm_containers).\nEmpty uses gtm.container_id from the config."
    • addedInput schema / properties / trigger_id / description
      Added value: +"Numeric GTM trigger ID, as listed by list_gtm_triggers or\na tag's firing/blocking triggers."
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "default": "",
+  "description": "Workspace to read (see list_gtm_workspaces), which\nincludes drafted changes that are not published yet. Empty reads\nthe live (published) container version.",
+  "type": "string"
+}
  2. Addedv0.12.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds real value beyond that by disclosing the error behavior for an unknown trigger_id and the live-vs-workspace read semantics. It does not cover auth requirements or rate limits, which are the only notable gaps.

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?

Front-loaded with the core action, then layered with payload contents, diagnostic purpose, and error behavior in short sentences. The enumerated field list is slightly long but each item earns its place by telling the agent what will come back.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the description still covers the key operational facts: read scope, error on bad ID, and what the config includes. Nothing critical is missing for a single-resource read tool.

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 description coverage is 100% and every parameter is already documented in-schema, so the baseline is 3. The description's note about workspace_id reading unpublished state largely restates the schema text rather than adding new syntax or format guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get the full RAW configuration for a single GTM trigger') and enumerates the payload contents (filters, auto-event filters, custom-event filters, validation settings, referencing tags). It is clearly distinguishable from siblings like list_gtm_triggers, get_gtm_tag, and get_gtm_workspace_diff.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete use case ('Helps diagnose why a tag with a specific trigger ID does or doesn't fire') and clarifies the read scope (live container vs. unpublished workspace state). It does not explicitly name alternatives such as get_gtm_tag or list_gtm_triggers, nor state when not to use it, so it stops short of full routing guidance.

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