Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

clients_create

Creates a new Google Tag Manager client by submitting a full JSON resource to a specified account, container, and workspace. Requires write access enabled and explicit confirmation.

Instructions

[WRITE] Create a new GTM client. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. Pass the full resource as a JSON string in bodyJson.

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>",
      "workspaceId": "<workspaceId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "clients_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull clients resource as a JSON string (e.g. {"name":"...","type":"..."}).
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does surface the most consequential behavioural facts: this is a write, it is gated behind an environment flag, and it requires an explicit confirm=true acknowledgement. It does not describe failure behaviour when the flag or confirm is missing, nor what the call returns, which keeps it below the top band.

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?

Three short sentences with the operation type front-loaded in brackets, followed by gating requirements, then the body format instruction. Nothing is redundant and no sentence can be removed without losing information.

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 5-required-parameter create tool with 100% schema coverage and no output schema, the description supplies the two things the schema cannot: the write gate and the confirm requirement. What remains thin is the outcome side — whether the created client is returned and in what shape — leaving a small gap for an agent that needs to chain the result.

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% and every parameter including confirm and bodyJson is already documented in the schema with types, patterns and the bodyJson example. The description restates the bodyJson convention ("full resource as a JSON string") without adding syntax, valid field values, or constraints beyond what the schema already provides, so the baseline of 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 ("Create a new GTM client") and prefixes the definition with a [WRITE] tag, which instantly separates it from clients_get, clients_list, clients_update and clients_delete in the sibling set. An agent can classify the tool without opening the schema.

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?

Gives explicit preconditions for invocation: GTM_MCP_ENABLE_WRITES=true and confirm=true must both be satisfied. What is missing is any explicit routing guidance (e.g. when to prefer clients_update instead, or what to do if the client already exists), so it stops short of full when/when-not coverage.

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