Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_event_create_rule

Deletes a GA4 event-create rule using its full resource name; requires confirm=true and the GA4_MCP_ENABLE_DELETES flag to execute.

Instructions

[GA4 DELETE] Delete an event-create rule. 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_event_create_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the event create rule to target: "properties/{property}/dataStreams/{stream}/eventCreateRules/{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 event create rule to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the event create rule to target: \"properties/{property}/dataStreams/{stream}/eventCreateRules/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/dataStreams\\/\\d+\\/eventCreateRules\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses that this is a delete operation plus two important safety gates: GA4_MCP_ENABLE_DELETES=true and confirm=true. It still does not state irreversibility, side effects, or permission details beyond the enable 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?

Two short sentences, front-loaded with the operation and immediately followed by the gating requirements. No unnecessary wording.

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 description supplies the key operational gate and confirmation requirement. It is nearly complete, though it could disclose irreversibility or return behavior.

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 100%, and the schema already explains both the full resource name format and that confirm must be true. The description adds no parameter meaning beyond that baseline.

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 (Delete) and resource (event-create rule), and the verb/resource pair separates it from sibling create/update tools for the same entity as well as other delete tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says what the tool deletes and gives prerequisites, but it does not explicitly say when to use this versus update/create alternatives or when not to delete. The intended usage is only implied by the operation.

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