Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

variables_list

Lists all user-defined GTM variables in a workspace and automatically follows pagination to return the complete set, with support for resuming truncated results.

Instructions

List all user-defined GTM variables in a workspace. Automatically follows pagination to return all variables.

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>"
    },
    "name": "variables_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
accountIdYes
pageTokenNoContinuation token to resume listing from a previous truncated result.
containerIdYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/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 behavioral burden and it does disclose one real trait: automatic pagination traversal. It omits the read-only implication, permission requirements, and — critically — the truncation behavior that the schema's maxPages parameter implies, so the picture is partial.

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 tight sentences, scope front-loaded, no filler. Every phrase carries information.

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?

A five-parameter, three-required tool with no annotations and no output schema needs more: the description should say what a variable record looks like at a high level and how truncation surfaces. As written it leaves the pagination-limit interaction and the three required identifiers unexplained.

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 40%, so the description should compensate, but it never mentions accountId, containerId, workspaceId, maxPages, or pageToken. Worse, "return all variables" sits awkwardly against the schema's maxPages default of 50 with truncated:true, which could lead an agent to assume a complete result set.

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 ("List all user-defined GTM variables") and scopes it to a workspace. The qualifier "user-defined" implicitly separates it from the built_in_variables_* siblings without naming them, so an agent can pick correctly.

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?

Usage is only implied by the purpose statement: an agent can infer this is the read/list operation for custom variables. There is no explicit when-to-use framing, no mention of when to prefer variables_get or the built-in variants, and no stated prerequisites beyond the workspace scope.

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