Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_list

Lists summary headers of every version in a Google Tag Manager container, enabling you to review version history by account and container ID with pagination and optional deleted-version inclusion.

Instructions

List all container version headers (summary) for a GTM container.

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

Input Schema

NameRequiredDescriptionDefault
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
accountIdYes
pageTokenNoContinuation token to resume listing from a previous truncated result.
containerIdYes
includeDeletedNoInclude deleted versions in results.

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 / maxPages / maximum
      Added value: +9007199254740991
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about the read-only nature, the default 50-page cap, or the truncated/nextPageToken behavior that the schema mentions. For a paginated listing tool with zero annotation coverage this is a meaningful gap.

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?

A single front-loaded sentence with no filler, but it is arguably too terse given the tool's parameter surface rather than wasteful.

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?

With five parameters, 60% schema coverage, no annotations and no output schema, the definition should explain listing scope, pagination defaults, and deleted-version behavior. As written it leaves the agent dependent on schema fragments for a non-trivial list operation.

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 only 60%, and the two required parameters (accountId, containerId) are documented only by a numeric pattern. The description's lone phrase "for a GTM container" does little more than gesture at containerId and says nothing about accountId or how the pagination/delete flags change results.

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 pairs a specific verb ("List") with a specific resource ("container version headers (summary)") scoped to a GTM container. The "headers (summary)" wording signals a lightweight listing as opposed to full version detail, which helps separate it from versions_get, though no sibling is named explicitly.

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 explicit when-to-use guidance, no mention of when to prefer versions_get for full detail, and no note on when includeDeleted or pagination controls matter. The only hint is the parenthetical "summary," which leaves the agent to infer the rest.

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