Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_firebase_link

Delete a Firebase link from a GA4 property using its full resource name and confirm=true; requires GA4_MCP_ENABLE_DELETES=true.

Instructions

[GA4 DELETE] Delete a Firebase link. 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_firebase_link"
  }
}

Input Schema

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

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose non-obvious behavioral facts: this is a destructive delete, it is gated behind an environment flag, and it needs explicit confirmation. It stops short of stating irreversibility or what a successful/failed response looks like.

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 prerequisites. Nothing is padded or redundant.

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 simple two-parameter delete with complete schema coverage and no output schema, the description covers the essentials an agent needs to attempt the call. Irreversibility and error-path behavior are the remaining gaps, minor for a tool this narrow.

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%, with both `name` (resource-name pattern) and `confirm` documented in the schema itself. The description only repeats that confirm must be true, adding no format or naming detail beyond the schema — baseline 3.

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 ("Delete a Firebase link") with the "[GA4 DELETE]" prefix reinforcing the operation class. The named resource type cleanly separates it from ga4_create_firebase_link and from the many other *_link delete siblings.

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?

Gives hard prerequisites (GA4_MCP_ENABLE_DELETES=true, confirm=true) that gate invocation, which is useful operational guidance. However, it offers no guidance on when to prefer this over related link-management tools or what to do when a delete is rejected or the link does not exist.

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