Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_list_containers

Read-onlyIdempotent

Lists Google Tag Manager containers for a specified account path, helping you inspect available containers before managing tags or settings.

Instructions

List containers in one GTM account.

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": {
      "account_path": "<account_path>"
    },
    "name": "gtm_list_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_pathYesaccounts/{account}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them: no pagination behavior, no result ordering, no permission requirements, and no statement of what a 'container' includes.

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?

A single short sentence, front-loaded with the verb and resource, with no filler. Nothing in it is redundant or padded.

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 simple one-parameter read tool with full annotation coverage and no output schema, the definition is minimally adequate. It is missing any hint about the return payload (a list of containers) or pagination, which would help an agent plan the call sequence.

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% and the single parameter account_path is documented with its format 'accounts/{account}', so the baseline is 3. The description adds no further meaning, such as how to obtain the account path or whether it can be derived from gtm_list_accounts.

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 (List) and resource (containers) plus a scoping constraint (one GTM account). It is clear what the tool does, but it does not distinguish itself from siblings like gtm_list_entities or gtm_list_accounts beyond the resource noun.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The only implied usage cue is the 'one GTM account' scope, which an agent must infer maps to the required account_path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.