Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

workspaces_create

Create a new Google Tag Manager workspace under a specified account and container; requires confirmation and write access enabled.

Instructions

[WRITE] Create a new workspace. Requires GTM_MCP_ENABLE_WRITES=true.

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": {
      "accountId": "<accountId>",
      "containerId": "<containerId>",
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "workspaces_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWorkspace name.
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
descriptionNoWorkspace description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / containerId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does flag the write nature and the env-var prerequisite. It does not mention that the schema requires confirm=true, nor discuss irreversible effects, required permissions, or what happens when the write gate is disabled (error vs no-op).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the write marker and the action, with no wasted words. The prerequisite is stated immediately after the purpose rather than buried.

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?

For a simple five-parameter create operation with a fully documented schema and no output schema, the description covers the action and the key operational prerequisite. The only meaningful omission is the missing description of failure behavior when the write flag is off.

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 every parameter including the confirm gate and the ID patterns is already documented in the schema. The description adds no parameter meaning beyond that, 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?

States a specific verb and resource ('Create a new workspace') and prefixes the definition with [WRITE], which immediately separates it from read siblings like workspaces_get and workspaces_list. It stops short of explicitly naming alternatives, but the operation is unambiguous.

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 only usage condition given is the environment gate GTM_MCP_ENABLE_WRITES=true, which is genuinely useful operational guidance. There is no explicit when-to-use guidance relative to workspaces_get/workspaces_list or containers_create, so the agent must infer that this tool is for creating brand-new workspaces.

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