Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_get

Retrieve the full contents of a specific GTM container version, or pass "live" as the version ID to inspect the currently live version.

Instructions

Get the full contents of a specific GTM container version. Pass "live" as containerVersionId to get the currently live version.

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

Input Schema

NameRequiredDescriptionDefault
accountIdYes
containerIdYes
containerVersionIdYesThe container version ID, or "live" for the current live version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / containerVersionId / pattern
      Added value: +"^(\\d+|live)$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Get' and 'full contents' establish a read operation that returns a large payload, but it says nothing about required permissions, error behavior for a nonexistent version, or whether the response includes tags/triggers/variables. Adequate but with clear gaps for a no-annotation tool.

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?

Two short sentences, front-loaded with the core action and followed by the one non-obvious parameter rule. The second sentence largely restates the schema's containerVersionId description, which is a minor redundancy rather than waste.

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?

For a simple read tool with three required parameters and no output schema, the definition covers the action, the resource scope, and the special 'live' value. What 'full contents' actually includes is left vague, which matters for a payload this large.

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 33%: containerVersionId is already documented in the schema with the exact 'live' semantics the description repeats, while accountId and containerId are undocumented in both places. The description therefore adds no meaning beyond the schema and does not compensate for the coverage gap.

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 ('Get the full contents of a specific GTM container version'), which separates it from versions_list by emphasizing retrieval of a single version's full body. It does not name any sibling explicitly, so differentiation relies on inference from the wording.

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 only usage guidance is the conditional 'Pass "live" as containerVersionId to get the currently live version,' which is genuinely useful. There is no guidance on how to obtain a numeric version ID (e.g., via versions_list) or when this is preferable to listing versions, so the routing context is only implied.

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