Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

clients_delete

Delete a GTM client by ID, with a required confirm flag. Enable deletes via GTM_MCP_ENABLE_DELETES and pass account, container, and workspace IDs.

Instructions

[DELETE] Delete a GTM client. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this delete operation.
clientIdYesThe clients ID to delete.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.

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 / clientId / 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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose an environment-level feature gate and a confirmation requirement that the agent otherwise could not know. It omits whether the delete is irreversible and whether dependent resources are affected, which matters for a destructive operation.

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 short sentences, front-loaded with the operation tag and the target resource, then the gating requirements. No filler or repetition.

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 five-required-parameter destructive tool with no output schema, the description covers the target resource and both invocation gates, which is enough to call it correctly. The remaining gap—reversibility and side effects of deleting a client—is a modest omission.

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 five parameters (accountId, containerId, workspaceId, clientId, confirm) are already documented in the schema. The description's mention of confirm=true echoes the schema text rather than adding new meaning, so the baseline of 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 names a specific verb and resource ('Delete a GTM client') and the '[DELETE]' prefix makes the operation class immediately scannable against siblings like clients_update and clients_revert. It stops short of explicitly contrasting with those siblings, but the purpose is unambiguous.

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?

It states two concrete prerequisites for invocation (GTM_MCP_ENABLE_DELETES=true and confirm=true), which is real when-to-use guidance. It does not explain when to prefer an alternative to deletion or what conditions make deletion inappropriate.

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