Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_key_event

Deletes a GA4 key event, reverting it to a normal event; requires explicit confirmation and delete opt-in.

Instructions

[GA4 DELETE] Delete a key event (it reverts to a normal event). 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": {
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "ga4_delete_key_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the key event to target: "properties/{property}/keyEvents/{id}".
confirmYesMust be true to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the key event to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the key event to target: \"properties/{property}/keyEvents/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/keyEvents\\/[A-Za-z0-9_-]+\\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 supplied, the description carries the full burden and does well: it discloses destructiveness, the actual effect (the event reverts to a normal event rather than being erased), and an environment-level safety gate. It does not say whether the action is reversible afterward or what the response contains, leaving some behavioral gaps for a mutation tool.

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?

A single front-loaded sentence plus a parenthetical, with zero filler. The verb and the most decision-relevant fact (the revert behavior) appear before the gate/confirm requirements.

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, the definition covers effect, safety gate, and confirmation. It omits what happens to historical event data after the revert and whether the deletion can be undone, which would matter to an agent planning a multi-step change.

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 both parameters, including the exact resource-name pattern for `name`, are already documented in the schema. The description only restates the `confirm=true` requirement, adding no new meaning such as how to obtain the key event ID. Baseline 3 applies when the schema does the work.

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 states a specific verb and resource ("Delete a key event") and immediately clarifies the semantic outcome ("it reverts to a normal event"), which separates it from ga4_update_key_event and ga4_create_key_event. The [GA4 DELETE] prefix reinforces the operation class before any prose is read.

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 a concrete precondition set (GA4_MCP_ENABLE_DELETES=true and confirm=true), which tells the agent exactly what must be true before calling. It stops short of naming an alternative path — e.g. that disabling key-event counting via update_key_event achieves a similar effect — so exclusions are absent.

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