Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_property

Soft-delete a GA4 property by moving it to trash, where it remains recoverable for a limited time before permanent removal. Requires delete enablement and confirm=true.

Instructions

[GA4 DELETE] Soft-delete (trash) a GA4 property. It is recoverable from the trash for a limited time, then permanently removed. 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": {
      "property": "<property>",
      "confirm": "<confirm>"
    },
    "name": "ga4_delete_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/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 the two most important traits: the operation is a recoverable soft-delete with a limited trash window before permanent removal, and it is gated behind an environment flag plus a confirm argument. It does not say what happens to child resources (data streams, key events, links), what permissions are required, or whether a restore path exists beyond the trash window.

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?

Three compact sentences with the destructive nature front-loaded before the prerequisites. Nothing is redundant, though the bracketed prefix is slightly noisy.

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 output schema and no annotations, the definition covers the essential decision inputs: what happens semantically, reversibility, and the safety gates. It falls short only on downstream effects on related resources and required permissions, which an agent might need before invoking a destructive call.

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 coverage is 50%: the schema documents 'property' with a format example and pattern, while 'confirm' is an undocumented boolean. The description partially compensates by stating confirm=true, implying it is an explicit safety acknowledgement rather than a functional input, but it adds no meaning to the property identifier beyond the schema.

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 ('Soft-delete (trash) a GA4 property') and immediately disambiguates the kind of deletion with the parenthetical 'trash', which separates it from siblings like ga4_delete_account or ga4_delete_data_stream. The '[GA4 DELETE]' prefix and the resource name make selection 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?

The description gives hard prerequisites ('Requires GA4_MCP_ENABLE_DELETES=true and confirm=true') but no explicit when-to-use vs. when-not guidance, nor does it point to an alternative such as updating the property instead. Usage is implied by the verb rather than reasoned about.

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