Skip to main content
Glama

AdLoop

by com.getadloop
OverviewDiscussionsAdmin

List Tag Manager triggers

list_gtm_triggers
Read-only

List every trigger in the LIVE GTM container, or in one workspace.

Each trigger has its filter conditions parsed to readable text (e.g. "{{Page Path}} matches RegExp ^/service-promotions/"). Helps diagnose why a tag fires or doesn't fire on specific pages. With workspace_id the list shows that workspace's unpublished state.

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

Input Schema

NameRequiredDescriptionDefault
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed2 schema fields changed
    • 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."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/openWorld, so safety is covered. The description adds real behavioral context beyond them: results are read from the LIVE published container unless a workspace_id is given, in which case unpublished drafted state is shown, and filter conditions are returned as readable text rather than raw objects.

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?

Front-loads the scope in the first sentence, uses a second only to explain the output shape and the diagnostic value, and closes with a one-line API reference. No filler.

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

Completeness5/5

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

With annotations covering safety, a 100%-covered schema, and an output schema handling return values, the description supplies everything else an agent needs: read scope, workspace behavior, and the diagnostic intent.

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%, so all three parameters including their sibling references and defaults are already documented. The description restates the workspace_id live-vs-draft semantics but adds no syntax or format detail beyond the schema, making 3 the correct baseline.

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 ('List every trigger') and precisely scopes it to the live container or a single workspace, which cleanly separates it from siblings like get_gtm_trigger and list_gtm_workspaces. It also previews what the output contains (parsed filter conditions).

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 (diagnosing why a tag fires or doesn't fire on specific pages) and explains the workspace_id branch's effect. It does not explicitly name alternatives such as get_gtm_trigger for a single trigger, 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.

All AdLoop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources