Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

zones_list

Lists all Google Tag Manager zones in a workspace, automatically following pagination and returning continuation tokens when results are truncated.

Instructions

List all GTM zones in a workspace. Automatically follows pagination.

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>"
    },
    "name": "zones_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.
accountIdYesThe GTM account ID.
pageTokenNoContinuation token to resume listing from a previous truncated result.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It does disclose a genuine behavioral trait - automatic pagination following - but omits that fetching is capped by maxPages (default 50) and can return truncated:true with a nextPageToken, and says nothing about required permissions or whether soft-deleted zones are included.

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, front-loaded sentences with no filler; the resource and scope come first and the behavioral note second. It is efficient, though the pagination sentence could have carried the truncation caveat at no extra cost.

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 list tool with five documented parameters and no output schema, the description covers what it does and a key behavioral trait (pagination) - but the sentence 'Automatically follows pagination' is only half true given the maxPages cap and truncation flag.

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 description coverage is 100%, so all five parameters (accountId, containerId, workspaceId, pageToken, maxPages) are already documented in the schema, including the truncation semantics. The description adds no meaning beyond that, so the baseline of 3 applies.

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 clear verb and resource ('List all GTM zones') plus scope ('in a workspace'), which separates it from zones_get, zones_create, and zones_update by their verbs. It stops short of explicitly naming the single-record sibling as the alternative, so it is clear but not maximally differentiating.

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 only implied by the phrase 'in a workspace' - an agent can infer this is the enumeration tool for zones. There is no explicit when-to-use guidance, no statement that zones_get should be used for a single known zone, and no prerequisites or exclusions.

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