Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

triggers_list

Lists all Google Tag Manager triggers in a workspace and follows pagination to return complete results.

Instructions

List all GTM triggers in a workspace. Automatically follows pagination to return all triggers.

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>"
    },
    "name": "triggers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
accountIdYes
pageTokenNoContinuation token to resume listing from a previous truncated result.
containerIdYes
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 / maxPages / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavioral trait: pagination is followed automatically so the caller receives the complete set. It does not state that the operation is read-only, what permissions the account/container/workspace IDs require, or that the internal page cap can cause a truncated result — that detail lives only in the maxPages schema text.

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?

Two short, front-loaded sentences with zero filler: the first identifies the resource and scope, the second adds the one non-obvious behavior. Nothing is redundant or padded.

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 straightforward list tool with no output schema, the description covers what is returned (all triggers, across pages) adequately. The major omission is any explanation of the three required identifier parameters and the container/workspace hierarchy, which is the main ambiguity an agent would hit when calling it.

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 coverage is only 40%: the three required IDs (accountId, containerId, workspaceId) have no schema descriptions at all. The description says only "in a workspace," which hints at workspaceId but leaves the required account/container hierarchy and the relationship between the three IDs unexplained, so it does not compensate for the gap. maxPages and pageToken are already documented in the schema.

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?

"List all GTM triggers in a workspace" gives a specific verb (list) and resource (GTM triggers) with an explicit scope (workspace), which separates it cleanly from triggers_get, triggers_create, and triggers_delete. It stops short of naming any sibling or contrasting behavior, so it is clear but not differentiating by guidance.

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?

Usage is implied by the word "list" and the workspace scope: reach for this when enumerating rather than fetching one trigger. There is no explicit statement of when to prefer triggers_get or when a full listing is overkill, and no prerequisites or exclusions are given.

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