Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

gtag_config_create

Create a new GTM gtag config by passing the full resource as a JSON string with account, container, and workspace IDs. Requires write access enabled and an explicit confirm flag.

Instructions

[WRITE] Create a new GTM gtag config. 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": "gtag_config_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull gtag configs 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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does add real value by disclosing the write gate and the explicit confirm requirement. It does not mention permission scope beyond the env flag, duplicate-name behavior, whether the write is reversible, or what a successful call returns, leaving meaningful gaps for a mutation.

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 class and resource up front, followed by prerequisites and the payload instruction. No filler, and the most decision-relevant information (write gate and confirm) appears before the bodyJson mechanics.

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?

All five required parameters are documented in the schema, and the description covers the write gating and payload form. However, there is no output schema, so the description should say something about the return value or error behavior for a create call, and it does not.

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 the schema already documents accountId, containerId, workspaceId, bodyJson, and confirm, so the baseline is 3. The description's note that bodyJson takes the full resource as a JSON string restates what the schema says rather than adding format or field-level detail.

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 states a specific verb and resource ("Create a new GTM gtag config") and flags the operation class with a [WRITE] prefix. It does not explicitly distinguish itself from the nearby gtag_config_update or gtag_config_get siblings, but the create semantics are 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 description names two hard preconditions (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is useful operational guidance. It stops short of when-to-use/when-not-to-use guidance relative to gtag_config_update or of stating what happens when the resource already exists, so usage selection is implied rather than explained.

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