Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_calculated_metric

Delete a GA4 calculated metric by full resource name. Requires confirmation and delete enablement.

Instructions

[GA4 DELETE] Delete a calculated metric. 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_calculated_metric"
  }
}

Input Schema

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

TDQS

B3.4/5.0
Behavior3/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 disclose two important gates: a server-side feature flag and a confirm flag. However, it never says whether deletion is permanent/irreversible, what permissions are needed, or what happens to dependent reports, which is the key behavioral fact 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, front-loaded sentences with the operation first and the prerequisites second; nothing is padded. The '[GA4 DELETE]' tag is slightly noisy meta-text but aids grouping.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 description covers the invocation gates but omits the consequences of calling it (permanence, error modes, side effects). Adequate to invoke correctly, incomplete for judging risk.

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 (the fully-patterned resource name and the confirm boolean) are already documented in the schema. The description only restates the confirm requirement and adds no new meaning about the name format or edge cases, so the baseline 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?

States a specific verb and resource: 'Delete a calculated metric', which the agent can immediately distinguish from the create/update/archive siblings. It does not name an alternative explicitly, but the verb+resource pairing 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?

The description supplies prerequisites (GA4_MCP_ENABLE_DELETES=true, confirm=true) rather than when-to-use guidance. There is no statement of when deletion is appropriate versus archiving a custom metric, and no exclusion or caution about irreversibility, so usage remains implied.

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