Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

workspace_sync

Syncs a GTM workspace to the latest container version by updating all unmodified entities and returns any merge conflicts.

Instructions

Syncs a workspace to the latest container version by updating all unmodified workspace entities. Returns a list of merge conflicts if any.

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

Input Schema

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

B3.4/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 does disclose two important behaviors: only unmodified entities are updated (modified ones are preserved) and conflicts are returned as a list rather than being auto-resolved. It does not say whether the operation is reversible, what permissions are required, or what happens on partial failure.

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?

Two compact sentences with the mechanism front-loaded and the return behavior second. Nothing is wasted, though it is arguably under-developed for a mutation rather than over-long.

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 four parameters are schema-documented and the description supplies the return behavior in lieu of an output schema. For a mutation with zero annotation coverage, however, it omits reversibility, permission requirements, and guidance on what to do with the returned conflicts, so it is adequate but not complete.

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%, so all four parameters including the confirm flag are already documented in the schema. The description adds no additional parameter meaning, so the baseline 3 applies.

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 ("Syncs a workspace") and explains the mechanism: updating all unmodified workspace entities to the latest container version. It does not name the related siblings such as workspace_resolve_conflict or workspace_get_status, so the boundary between them is left implicit.

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 implied by the word "Syncs" but there is no explicit when-to-use guidance, no statement of preconditions, and no routing to alternatives like workspace_resolve_conflict for the conflicts this tool returns. The confirm gate exists only in the schema, not the prose.

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