Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_sync_workspace

Sync a Google Tag Manager workspace to the current container version after explicit user confirmation, keeping approved GTM changes aligned with the live container.

Instructions

Sync a GTM workspace to the latest container version. Requires explicit user confirmation.

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_path": "<workspace_path>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_sync_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
change_summaryYesConcise exact change the user approved in the current request.
user_confirmedYesMust be true only after explicit action-time user confirmation.
workspace_pathYes

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?

The annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the agent knows the operation is non-idempotent and open-world. The description adds the confirmation requirement, which is useful behavior context, but it does not say what happens to existing workspace/container state after the sync, whether conflicts are possible, or what the result looks like, so the extra context is limited.

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?

Two short sentences, zero filler, with the core action front-loaded ahead of the prerequisite. It could have been trimmed slightly differently but every sentence carries information.

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 an open-world, non-idempotent mutation with no output schema, the definition covers the action and the confirmation gate but leaves out the post-sync state, whether workspace changes are overwritten, and any conflict behavior. Those are material gaps for an agent deciding whether to call it, but the core is adequate.

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 coverage is 67%, and change_summary and user_confirmed are already well documented in the schema, including the const true constraint. The description only reinforces the confirmation requirement already encoded by user_confirmed, and workspace_path remains undocumented in both places, so it adds little meaning beyond the structured fields.

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 uses a specific verb and resource ("Sync a GTM workspace") and names the target state ("the latest container version"), so the action is unambiguous. It does not name any sibling or explain how it differs from gtm_create_version or gtm_publish_version, which keeps it from a 5.

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?

It states one hard prerequisite: "Requires explicit user confirmation", which tells the agent about a gating condition before invoking it. It gives no guidance on when to choose this over sibling version tools (for example, gtm_create_version or gtm_publish_version), so the usage context is only implied.

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