Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_set_latest

Sets a chosen container version as latest and syncs the default workspace to it. This does not publish; use versions_publish to go live.

Instructions

[WRITE] Set a specific container version as the "latest" (synchronizes the default workspace with this version). Note: This does NOT publish. Use versions_publish to go live. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
containerIdYes
containerVersionIdYesThe version ID to set as latest.

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+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it marks the tool as a write, discloses the side effect on the default workspace, and states the environment/confirm gating. It stops short of saying whether the change is reversible, what permissions are needed, or what happens to a workspace that already has unsynced edits.

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-loaded with the action and a bracketed [WRITE] marker, followed by the scope caveat, the alternative, then the prerequisites. Every sentence carries distinct information with no repetition.

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 four-required-parameter mutation tool with no annotations and no output schema, the definition covers the safety profile, the side effect, and the wrong-tool trap. The remaining gap is the two unexplained ID parameters and any hint about the response shape, which is minor given the mutation semantics are otherwise well covered.

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 coverage is only 25% — containerVersionId is the sole documented parameter — but the description adds real meaning for confirm by tying it to the write gate. accountId and containerId remain unexplained in both places, and there is no note on where the version ID must come from (e.g., versions_list).

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 and resource ("Set a specific container version as the 'latest'") and immediately scopes the effect with "synchronizes the default workspace with this version". The parenthetical "This does NOT publish" plus the named sibling versions_publish lets an agent separate this from the nearest look-alike without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the condition that selects it: "This does NOT publish. Use versions_publish to go live." It also states the preconditions for invocation (GTM_MCP_ENABLE_WRITES=true and confirm=true), so the agent knows both when to pick this tool and when it can be called at all.

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