Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

workspace_get_status

Retrieve a GTM workspace's changed entities and merge conflicts so you can review the change diff before creating a version or publishing.

Instructions

Get the status of a GTM workspace: the list of changed entities (workspaceChange) relative to the latest container version, plus any merge conflicts. Use this to review a change diff before creating a version or publishing.

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": "workspace_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observedv1.0.0

TDQS

A4/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 burden. It implies a read-only inspection and discloses the payload contents (diff plus merge conflicts), which is meaningful context. However, it says nothing about required permissions, whether conflicts block subsequent publishing, or pagination/size characteristics of large diffs.

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 sentences with no filler: the first defines the output, the second defines the use case. The most decision-relevant content (what the diff is relative to) is front-loaded.

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?

All three required identifiers are documented in the schema and, with no output schema present, the description steps in to explain the return value (changed entities and merge conflicts). What's missing is only peripheral behavioral detail, such as permissions or how conflicts are cleared.

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 each of accountId, containerId, and workspaceId carries its own description with format constraints, so the schema does the work. The description adds no extra meaning about the identifiers or how scoping affects the returned diff, which is the expected baseline.

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 names a specific verb and resource (get the status of a GTM workspace) and enumerates exactly what comes back: workspaceChange entries relative to the latest container version plus merge conflicts. An agent can tell this apart from workspace_create_version_and_publish or workspace_sync without opening any 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?

It states a concrete use case — review the change diff before creating a version or publishing — which gives clear when-to-use context. It does not spell out exclusions, e.g., that workspace_resolve_conflict is the tool for fixing the conflicts this one surfaces, so a small gap remains.

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