Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

containers_list

Lists Google Tag Manager containers in a specified GTM account and automatically follows pagination to return every container, with page-token support for truncated results.

Instructions

List all GTM containers within a GTM account. Automatically follows pagination to return all containers.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / maxPages / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

A3.6/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 behavioral burden, and it does disclose the key trait: pagination is followed automatically so the caller receives the complete set rather than one page. It says nothing about permission requirements for reading a container, result ordering, or the fact that results can be truncated when maxPages is exceeded — the latter only appears in the schema.

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 short sentences, zero filler, and the scope statement is front-loaded before the pagination behavior. Nothing could be removed without losing information.

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 simple read-only listing tool with three fully documented parameters and no output schema, the definition covers purpose, scope, and the one non-obvious behavior (automatic pagination). A brief note on what a container record contains or how results are ordered would close the remaining gap.

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 accountId, maxPages, and pageToken are already fully documented, making 3 the baseline. The phrase "within a GTM account" corroborates the accountId scoping but adds no format or constraint detail beyond the schema.

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 specific verb and resource ("List all GTM containers") plus the scoping boundary ("within a GTM account"), which is enough to distinguish it from the single-object siblings like containers_get or containers_lookup. It stops short of naming those alternatives explicitly, so it lands just under the top score.

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 by the enumeration framing — call it when you need every container in an account — but there is no explicit when-to-use vs. when-to-use-a-sibling guidance (e.g. use containers_get for one known container). An agent must infer routing from sibling names alone.

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