Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

workspace_create_version_and_publish

Creates a new container version from a workspace and immediately publishes it to production.

Instructions

[PUBLISH] Create a new container version from a workspace and immediately publish it. Requires GTM_MCP_ENABLE_PUBLISH=true and confirm=true. ⚠️ This is the most powerful write operation — it goes live in production immediately.

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

Input Schema

NameRequiredDescriptionDefault
nameNoVersion name.
notesNoVersion notes.
confirmYesMust be true to confirm this publish operation.
accountIdYes
containerIdYes
workspaceIdYes

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

TDQS

A3.7/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 discloses an environment gate, a mandatory confirmation flag, and warns that this is the most powerful write operation going live in production immediately. It leaves unstated whether the operation is reversible, how to roll back, or what happens if publish fails after the version is created.

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?

Three short sentences, front-loaded with the action and danger signal, with zero padding. The gating requirement is stated twice in close succession (env flag and confirm), a small duplication that costs it a point.

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 high-stakes mutation with no annotations and no output schema, the description covers the essentials an agent needs before invoking: what it does, the gates, and the production impact. Missing are failure semantics, reversibility, and any hint about permissions or what the call returns.

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 50% (name, notes, confirm documented; accountId/containerId/workspaceId not). The description reinforces that confirm must be true but adds no format, scoping, or default guidance for the three ID parameters, so it only partially compensates 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?

"[PUBLISH] Create a new container version from a workspace and immediately publish it" states a specific verb (create + publish) and resource (container version from workspace), so an agent knows exactly what the tool produces. It does not explicitly contrast with the sibling versions_publish (publishing an existing version vs. creating one), which keeps it short of a 5.

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 rather than spelled out: the tool is for when you want the workspace state to go live now, and it names prerequisites (GTM_MCP_ENABLE_PUBLISH=true, confirm=true). It never says what to do instead when only a version should be created without publishing, or whether preview/status checks should precede it.

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