Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_firebase_link

Creates a Firebase link for a GA4 property by specifying the property ID and Firebase project; confirmation is required to apply the change.

Instructions

[GA4 WRITE] Create a Firebase link (no update; delete + recreate to change). Requires GA4_MCP_ENABLE_WRITES=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>",
      "project": "<project>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_firebase_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to apply the change.
projectYesFirebase project id or number ("projects/{id}").
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.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A4.2/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 the two things that matter most: a global write gate and a mandatory confirm flag, plus the fact that the link cannot be modified in place. It stops short of describing what the link actually attaches (e.g. which property↔project integration is created) or any side effects/side effects on existing links.

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 compact clauses, front-loaded with a [GA4 WRITE] tag that signals risk before the substance. No filler sentences.

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 three-required-parameter mutation tool with no output schema and no annotations, the description covers the safety gates and immutability constraint that an agent needs to act correctly. Only the effect of the operation itself (what a Firebase link is and what gets changed) is left implicit.

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 each of property, project and confirm already documented in the schema, so the baseline is 3. The description adds nothing parameter-level beyond restating that confirm is required.

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 (create a Firebase link) and immediately bounds the semantics with '(no update; delete + recreate to change)', which is a real distinction from the update_* siblings. An agent can classify this tool without opening the schema.

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?

Gives the preconditions for use (GA4_MCP_ENABLE_WRITES=true and confirm=true) and tells the agent what to do if the link already exists (delete and recreate). It doesn't name ga4_delete_firebase_link explicitly, so routing is inferred rather than spelled out.

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