Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_get_version

Read-onlyIdempotent

Fetches a Google Tag Manager container version and all its entities, enabling inspection of tags, triggers, and variables for a specified version path.

Instructions

Get a GTM container version and all of its entities.

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": {
      "version_path": "<version_path>"
    },
    "name": "gtm_get_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
version_pathYesaccounts/{account}/containers/{container}/versions/{version}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds one useful behavioral fact — that the response bundles the version with all of its entities, implying a potentially large payload — but says nothing about size, pagination, or error behavior on a bad path.

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 and the key scope qualifier in the right place. It is efficient, though the brevity leaves little room for the disambiguation that the sibling set would reward.

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 rich annotations, the description covers the core purpose and the aggregate return nature. With no output schema, it could still say more about what 'entities' includes or the response shape, so it is adequate but not complete.

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 version_path parameter is documented with its full resource-name template, so the schema carries the parameter burden. The description adds no meaning beyond that, which is the expected baseline for a fully documented one-param 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?

The description gives a specific verb and resource ('Get a GTM container version') and adds scope ('and all of its entities'), which distinguishes it from entity-level siblings like gtm_get_entity. It stops short of naming an alternative explicitly, so an agent must still infer which sibling to pick.

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 rather than stated: 'all of its entities' hints this is the whole-version fetch as opposed to a single-entity lookup, but there are no explicit when-to-use/when-not rules and no prerequisites (e.g., read permissions, published vs. unpublished versions).

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