Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

triggers_get

Retrieve a specific Google Tag Manager trigger by account, container, workspace, and trigger ID to inspect its configuration.

Instructions

Get a specific GTM trigger.

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

Input Schema

NameRequiredDescriptionDefault
accountIdYes
triggerIdYes
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 / triggerId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the word "Get". It does not state that the operation is read-only, what permissions or workspace scoping are required, or what happens when the trigger ID does not exist. Only the implicit read semantics of "Get" provide any signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and contains no filler, which is structurally sound. The terseness is under-specification rather than true conciseness, so it earns only a middling score.

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 tool requiring four nested-identifier parameters with no annotations and no output schema, the definition is far too sparse. An agent cannot tell from the description alone how to construct a valid call or what the response will contain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters (accountId, containerId, workspaceId, triggerId) are required with 0% schema description coverage, and the description explains none of them. It does not clarify the hierarchical relationship between account, container, and workspace, nor the numeric-string pattern constraints.

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

Purpose3/5

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

"Get a specific GTM trigger" states a verb and a resource, and "specific" signals single-item retrieval rather than a list, which separates it from triggers_list. However, it names no identifying fields and does not explicitly distinguish itself from the other trigger siblings, so the purpose is adequate but thin.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as triggers_list or triggers_update. The agent must infer that this is the single-record read path from the name alone.

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