Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Tag Manager version details

get_gtm_version
Read-only

Retrieve metadata, entity counts, version notes, fingerprint, and tag/trigger/variable names for a specific Google Tag Manager container version to inspect its configuration.

Instructions

Get metadata + entity counts for a single GTM container version.

Returns name, description (the version notes), fingerprint, and lists of tag/trigger/variable names at that point in time. The API returns no timestamps or author for a version.

Tag Manager API: https://developers.google.com/tag-platform/tag-manager/api/v2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gtm_account_idNoNumeric GTM account ID (see list_gtm_accounts). Empty uses gtm.account_id from the config.
gtm_container_idNoNumeric GTM container ID (see list_gtm_containers). Empty uses gtm.container_id from the config.
container_version_idYesNumeric container version ID from list_gtm_versions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / container_version_id / description
      Added value: +"Numeric container version ID from\nlist_gtm_versions."
    • addedInput schema / properties / gtm_account_id / description
      Added value: +"Numeric GTM account ID (see list_gtm_accounts). Empty\nuses gtm.account_id from the config."
    • addedInput schema / properties / gtm_container_id / description
      Added value: +"Numeric GTM container ID (see list_gtm_containers).\nEmpty uses gtm.container_id from the config."
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. Addedv0.12.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true/openWorldHint=true, and the description goes beyond them with a genuinely useful disclosure: the API returns no timestamps or author for a version, which stops an agent from requesting fields that do not exist. It also enumerates the returned entity kinds, though it says nothing about permissions or pagination.

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?

Front-loaded with the core purpose, then the return content, then the limitation note; each sentence carries information. The trailing API documentation URL is slightly expendable but harmless.

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?

With an output schema present, the description does not need to enumerate return values, yet it summarizes them helpfully and flags the version's data limitations. Nothing critical for a correct one-shot call appears to be missing.

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 three parameters (account ID, container ID, container version ID) are already documented with fallback behavior and cross-references. The description adds no additional parameter meaning, which is the expected baseline when the schema does the work.

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 opens with a specific verb+resource ('Get metadata + entity counts for a single GTM container version') and lists concrete returned fields, so the tool's purpose is unambiguous. It does not, however, explicitly distinguish itself from close siblings such as list_gtm_versions or get_gtm_version_diff beyond the word 'single'.

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: 'single GTM container version' hints this is the detail lookup versus the list tool, but there is no explicit when-to-use, when-not-to-use, or pointer to get_gtm_version_diff for comparisons. An agent must infer the selection rule from sibling names.

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