Skip to main content
Glama
samarthanalytics-sj

Samarth GTM MCP Server

Official

variables_create

Creates a new GTM variable with specified name, type, and parameters. Requires confirmation and write mode enabled.

Instructions

[WRITE] Create a GTM variable. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesVariable name.
typeYesVariable type (e.g. "v" for data layer, "k" for first-party cookie, "u" for URL, "c" for constant, "jsm" for custom JS, "smm" for lookup table, "gas" for GA settings).
notesNo
confirmYes
accountIdYes
parameterNoGTM parameter list — supports NESTED list/map params. Example (a GA4 event parameter table): [{"type":"list","key":"eventSettingsTable","list":[{"type":"map","map":[{"type":"template","key":"parameter","value":"click_text"},{"type":"template","key":"parameterValue","value":"{{Click Text}}"}]}]}].
containerIdYes
workspaceIdYes
parentFolderIdNo
enablingTriggerIdNo
disablingTriggerIdNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only notes the write nature and conditional flags but does not disclose behavioral traits like conflict handling, rate limits, or what happens on success/failure. The '[WRITE]' prefix is a minimal behavioral hint, but overall transparency is low.

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?

The description is extremely concise with one sentence and a flag note. It is front-loaded with the verb and resource. While efficient, it may be too brief for the tool's complexity, but it wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 11 parameters (6 required) and no output schema or annotations, the description is incomplete. It does not explain return values, error cases, or how the creation process works (e.g., immediate persistence). The brevity leaves significant gaps for a complex operation.

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?

Schema description coverage is only 27%, meaning most parameters lack explanations. The description adds no parameter information beyond the schema, failing to compensate for the low coverage. Users get no additional clarity about parameter usage or constraints.

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?

The description clearly states 'Create a GTM variable' with a '[WRITE]' prefix indicating the operation type. Among sibling tools (variables_delete, variables_get, variables_list, variables_update), this uniquely identifies the creation action, making the purpose specific and distinguishable.

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 mentions required flags (GTM_MCP_ENABLE_WRITES=true and confirm=true) as prerequisites, implying usage conditions. However, it provides no guidance on when to use this tool versus alternatives (e.g., when to create vs update) or scenarios where it should not be used, leaving usage context implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samarthanalytics-sj/samarth-analytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server