Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_list_version_headers

Read-onlyIdempotent

Lists Google Tag Manager container version headers, including published and previous versions, so you can review version history for a given container path.

Instructions

List GTM container version headers, including published and previous versions.

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": {
      "container_path": "<container_path>"
    },
    "name": "gtm_list_version_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
container_pathYesaccounts/{account}/containers/{container}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

While annotations handle safety (read-only, idempotent), the description adds crucial context regarding scope by explicitly stating it includes 'published and previous versions.' This manages the user's expectations about the data returned beyond a simple list.

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?

The definition is highly efficient, consisting of a single, punchy sentence. It is perfectly sized and front-loaded without any superfluous wording.

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?

The definition is nearly complete. It covers the resource and its version history scope well. Its only small gap is not specifying behavioral aspects like pagination or whether it returns only headers or full version metadata.

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?

Since the input schema coverage is 100%, the schema already details the required `container_path`. The description does not add semantic meaning to the parameter's value beyond what the structure already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a specific action (List) applied to a clear resource (GTM container version headers). It successfully differentiates itself from sibling tools that might focus on creating or retrieving a single version.

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?

The description is clear on what the tool does, but it does not explicitly advise when to use it versus other listing or version management tools. This is a minor omission.

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