Skip to main content
Glama
Sign In
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Tag Manager workspace changes

get_gtm_workspace_diff
Read-only

Inspect drafted, unpublished GTM workspace changes, including added, modified, or deleted tags, triggers, and variables plus merge conflicts, before publishing.

Instructions

Show drafted-but-not-published changes in a GTM workspace.

Returns the list of entities (tags, triggers, variables) added, modified, or deleted relative to the live published version, plus any merge conflicts. Common cause of "I edited a tag but nothing happened" — the workspace was never published. is_clean=true means no pending changes and no conflicts.

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

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_gtm_workspace_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesNumeric GTM workspace ID from list_gtm_workspaces.
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • 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."
    • addedInput schema / properties / workspace_id / description
      Added value: +"Numeric GTM workspace ID from list_gtm_workspaces."
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. Addedv0.12.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real beyond-annotation context: the return set (added/modified/deleted tags, triggers, variables), merge conflicts, and the meaning of is_clean=true.

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 useful return-shape and diagnostic context, ending with the API reference. The 'Common cause of...' sentence earns its place by clarifying usage, though the definition runs slightly long.

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?

An output schema exists, so return values are largely documented structurally, yet the description still summarizes the key fields and is_clean semantics. Combined with annotations covering safety, the definition is essentially complete for correct invocation.

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 workspace_id, gtm_account_id, and gtm_container_id are already documented with defaults and cross-references. The description adds no parameter-level detail, so the baseline 3 applies.

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?

Clear specific verb+resource: 'Show drafted-but-not-published changes in a GTM workspace,' with scope pinned to 'relative to the live published version.' An agent can tell it is a workspace-diff reader. It does not name its closest sibling (get_gtm_version_diff), so it stops short of full differentiation.

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?

Provides a concrete diagnostic scenario ('I edited a tag but nothing happened') that cues when to reach for this tool. It gives clear context but no explicit exclusions or named alternatives against get_gtm_version_diff.

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