Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_undelete

Restore a previously deleted GTM container version. Requires write access enabled and explicit confirmation per call.

Instructions

[WRITE] Undelete a previously deleted GTM container version. 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_undelete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
containerIdYes
containerVersionIdYes

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

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the write gate and the confirm requirement — behavior not derivable from the schema. However, it says nothing about what undelete actually restores, whether it errors if the version is not deleted, permission requirements, or reversibility of the operation.

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 tight sentences with the '[WRITE]' marker front-loaded followed by purpose and then prerequisites — no filler and no redundancy.

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 mutation tool with zero annotation coverage, no output schema, and undocumented parameters, the description covers the invocation gate but leaves the effect and failure semantics unexplained. It is adequate to prevent an accidental call but thin for predicting what the call will do.

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 description coverage is 0%, so the description must compensate for all four parameters. It only explains confirm (that it must be true to proceed); the three ID parameters are left entirely to their self-describing names and numeric patterns, with no added meaning about which account/container/version they scope.

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?

The description gives a specific verb+resource pair ('Undelete a previously deleted GTM container version') and prefixes it with '[WRITE]', so an agent immediately knows the operation and its mutation class. It is distinguishable from the sibling versions_delete by the 'previously deleted' framing, though it never names the sibling explicitly.

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?

It states the two preconditions for invocation (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is genuine when-to-use guidance. It does not say when not to use it (e.g., when a version is not deleted, or when to prefer versions_get / versions_publish instead), so usage is implied rather than fully routed.

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