Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_account

Soft-delete (trash) an entire GA4 account and all its properties, with recovery available for a limited time; requires explicit confirmation and deletes enabled.

Instructions

[GA4 DELETE] Soft-delete (trash) an entire GA4 account and all its properties. High blast radius — recoverable from the trash for a limited time. Requires GA4_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>",
      "confirm": "<confirm>"
    },
    "name": "ga4_delete_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / accountId / minLength
      Removed value: -1
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\s*(accounts\\/)?\\d+\\s*$"
  2. Addedv1.160.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that the delete is a soft-delete to trash, that recovery is time-limited, that the blast radius covers all properties, and that two preconditions (env flag and confirm=true) gate execution. It does not describe what is returned on success or how failures surface, which keeps it below a 5.

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 tightly written sentences with zero filler. The destructive scope is front-loaded in the first clause, and the safety requirements are packed into the second, so the most decision-relevant information arrives first.

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 two-parameter destructive tool with no annotations and no output schema, the description covers the essentials: what is deleted, how recoverable it is, and what must be true before calling. The only gap is return/failure behavior, which is minor here given there is no output schema to rely on.

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 0%, so the description must compensate. It clarifies that 'confirm' must be true rather than merely present, which is real added meaning, but 'accountId' is only implicitly referenced through 'entire GA4 account' — the accepted numeric or 'accounts/{id}' format from the schema pattern is not explained.

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 uses a specific verb and resource — 'Soft-delete (trash) an entire GA4 account and all its properties' — and explicitly scopes it to a whole account, which separates it from sibling tools that delete individual properties, links, or bindings. An agent can identify the target and magnitude without opening the 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 gives clear preconditions for use (GA4_MCP_ENABLE_DELETES=true and confirm=true) and signals that this is the high-blast-radius option ('entire GA4 account and all its properties'), implying narrower delete tools exist for sub-resources. It stops short of naming a specific alternative for deleting a single property, so no explicit exclusion or routing sentence is present.

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