Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_create_workspace

Creates a Google Tag Manager workspace in a specified container after explicit user confirmation, so approved GTM changes can be prepared in an isolated workspace.

Instructions

Create a GTM workspace. Requires explicit user confirmation in the current request.

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": {
      "container_path": "<container_path>",
      "name": "<name>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo
change_summaryYesConcise exact change the user approved in the current request.
container_pathYesaccounts/{account}/containers/{container}
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so safety and idempotency are covered structurally. The description adds the non-obvious confirmation precondition, which is real behavioral value, but says nothing about post-creation state (is it a draft workspace? does it inherit container contents?), which matters for a mutation tool.

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, front-loaded with the action and immediately followed by the constraint. Nothing is padded, though the phrasing is telegraphic enough that it reads as a fragment rather than a fully formed instruction.

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 four-required-parameter mutation with no output schema, the definition covers the safety-critical bit (confirmation) but omits what the caller gets back (a workspace path/name, presumably needed for subsequent gtm_create_version calls) and what the new workspace contains. Adequate to avoid a wrong call, thin for chaining calls correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description names no parameters at all. With 60% schema coverage, container_path, change_summary, and user_confirmed are documented in the schema, but name and description are not, and the description does not compensate for that gap or clarify the format of container_path beyond what the schema states.

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?

States a specific verb and resource ("Create a GTM workspace"), which is distinguishable from siblings like gtm_create_version and gtm_create_entity by resource type. It does not, however, explicitly contrast itself with those siblings or with gtm_list_workspaces, so the differentiation is implicit rather than stated.

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?

The second sentence gives a hard gating condition — explicit user confirmation must exist in the current request — which is genuine usage guidance. There is no guidance on when a new workspace is preferable to an existing one (e.g., via gtm_list_workspaces) or on container/account prerequisites, so alternatives remain unaddressed.

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