AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Draft rolling back Tag Manager to a version

draft_rollback_gtm_version

Destructive

Preview republishing an older Google Tag Manager container version live. See all tag, trigger, and variable changes before applying, with safeguards if live changed.

Instructions

Draft republishing an older Tag Manager version LIVE; returns a PREVIEW.

A rollback publishes an existing container version again. The preview diffs the live version against the target, so it lists every tag, trigger and variable that changes on the site, and it pins the live version: apply refuses when another version went live after the preview, or when the target was modified or archived. Workspaces are not changed. Refused unless gtm.write_enabled is set, and refused when the target adds or changes a Custom HTML tag while gtm.allow_custom_html is off. Returns the diff, previous_live_version_id (the version that restores today's state), the target version and a plan_id.

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

Input Schema

TableJSON Schema

Name	Required	Description
`version_id`	Yes	Container version ID to make live again (see list_gtm_versions and get_gtm_version_diff).
`gtm_account_id`	No	Numeric GTM account ID (see list_gtm_accounts). Empty uses gtm.account_id from the config.
`gtm_container_id`	No	Numeric GTM container ID (see list_gtm_containers). Empty uses gtm.container_id from the config.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.27.1Oct 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Far exceeds the annotations: it discloses the version pinning, that apply will refuse if another version went live, that workspaces are untouched, the gtm.write_enabled and gtm.allow_custom_html preconditions, and the returned artifacts (diff, previous_live_version_id, plan_id). This is unusually rich behavioral context for a destructive draft operation.

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-loads the crucial insight (drafts a live rollback and returns a preview) in the first sentence. Dense but nearly every sentence carries distinct value; a couple of long compound sentences could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even with an output schema present, the description covers preconditions, refusal behavior, side effects and return contents, making it complete for a complex destructive mutation.

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 the schema already documents all three parameters with cross-references. The description adds conceptual framing of the target version but no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource: "Draft republishing an older Tag Manager version LIVE; returns a PREVIEW." The second sentence explicitly defines rollback semantics, distinguishing it from sibling publish/version tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the rollback context and names related tools (list_gtm_versions, get_gtm_version_diff) for the target version. It does not explicitly contrast with draft_publish_gtm_workspace or state when-not-to-use, but the rollback-vs-publish concept is clearly conveyed.

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

Deploy Server