Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

folders_delete

Delete a GTM folder while keeping its contents by moving them to the workspace root, not deleting them. Requires delete flag enabled and per-call confirmation.

Instructions

[DELETE] Delete a GTM folder. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true. Contents of the folder will be unfoldered, not deleted.

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

Input Schema

NameRequiredDescriptionDefault
confirmYes
folderIdYes
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 / folderId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses that a feature flag gates the operation, that confirm must be explicitly set, and critically that folder contents are unfoldered rather than deleted. It omits irreversibility/recovery behavior and any permission requirements beyond the env flag.

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?

Three short sentences, front-loaded with the operation and gated requirements, ending with the most surprising behavioral fact. No filler or restatement.

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?

For a destructive 5-parameter mutation with no annotations and no output schema, this covers the essentials: gating flags and the side effect on contained entities. Minor gaps remain around failure modes and what the response contains, though no output schema exists to defer to.

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 0% across five required parameters, and the description only explains the semantics of confirm. accountId, containerId, workspaceId, and folderId are left entirely to their self-evident names, with no indication of ID format, hierarchy, or whether the workspace must be the default workspace.

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?

States a specific verb and resource: "[DELETE] Delete a GTM folder." The bracketed operation tag plus the explicit resource type distinguishes it immediately from sibling folders_create, folders_update, and folders_entities.

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?

Gives concrete preconditions for invocation: GTM_MCP_ENABLE_DELETES=true and confirm=true, which tells an agent when the call is permitted. It does not name alternatives (e.g., folders_move_entities or folders_update as safer options) or state when deletion is the wrong choice, so it stops short of full routing guidance.

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