Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

export_container

Exports a GTM workspace summary as structured JSON, including tags, triggers, variables, folders, and built-in variables for documentation, auditing, or data reuse.

Instructions

Export a full GTM workspace summary as structured JSON. Returns all tags, triggers, variables, folders, and built-in variables. This is a read-only operation. Use this for documentation, auditing, or feeding container data to other tools.

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

Input Schema

NameRequiredDescriptionDefault
formatNo"full" = all fields, "summary" = key fields only, "names_only" = just names and IDssummary
maxPagesNoMaximum API pages to fetch PER collection (default 50); the five collections are paged independently, so maxPages:2 costs up to 10 API pages. If more remain, the export is marked incomplete:true with truncatedCollections and per-collection nextPageTokens.
accountIdYes
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. Changed1 schema field changedv1.451.2
    • addedInput schema / properties / maxPages
      Added value: +{
      +  "description": "Maximum API pages to fetch PER collection (default 50); the five collections are paged independently, so maxPages:2 costs up to 10 API pages. If more remain, the export is marked incomplete:true with truncatedCollections and per-collection nextPageTokens.",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
  3. Addedv1.421.0
  4. Removedv1.350.0
  5. First observedv1.0.0

TDQS

A3.6/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; it does state "read-only operation" and lists the returned collections, which is real value. However, it omits what happens when pagination limits are hit (incompleteness flag, truncatedCollections, nextPageTokens) and gives no auth or scoping prerequisites, even though the schema's maxPages note reveals truncation is a real behavior.

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?

Four short sentences, front-loaded with the action and payload, and the read-only sentence earns its place by setting the safety expectation. Minor redundancy between "full ... summary" and the schema's format default keeps it from being maximally tight.

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?

There is no output schema, so the description reasonably summarizes the return shape, and that is its strongest contribution. For a 5-parameter export tool, it still leaves out truncation/pagination semantics and the prerequisites implied by accountId/containerId/workspaceId, leaving gaps the agent must fill from the schema alone.

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 only 40%, but the two substantive parameters (format, maxPages) are documented thoroughly in the schema, while the three remaining parameters are numeric ID patterns that need little explanation. The description itself adds nothing about format modes or pagination; its phrase "full ... summary" is slightly at odds with the default format of "summary".

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 ("Export") and resource ("full GTM workspace summary as structured JSON") and enumerates what the export contains: tags, triggers, variables, folders, built-in variables. It does not name or differentiate itself from sibling tools such as audit_container or containers_get, so an agent must infer the boundary.

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?

Provides concrete usage contexts: documentation, auditing, or feeding container data to other tools. It gives no when-not conditions and does not route the agent away from audit_container, which is the likely adjacent choice, so the guidance is clear but not complete.

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