Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_google_ads_link

Creates a Google Ads link for a GA4 property to connect Ads data when write access is enabled and the change is confirmed.

Instructions

[GA4 WRITE] Create a Google Ads link. 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>",
      "customerId": "<customerId>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_google_ads_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
customerIdYesGoogle Ads customer ID (digits, no dashes).
adsPersonalizationEnabledNo

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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden, and it does disclose the most important trait: this is a write, gated behind an environment flag and an explicit confirm flag. It stops short of describing side effects, whether the operation is idempotent or fails on duplicate links, and what permissions the Google Ads customer ID requires.

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 write marker and the action, followed by the gating conditions. There is no filler or restated title text.

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 4-parameter mutation with no annotations and no output schema, the definition covers the safety gate but not the result of the call or the meaning of adsPersonalizationEnabled. An agent could invoke it correctly on the happy path but lacks information about failure modes and the optional flag.

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 75%, with property, customerId, and confirm documented in the schema itself. The description adds nothing about parameters, and adsPersonalizationEnabled has no schema description at all, leaving its default and effect unexplained in both places.

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?

The description states a specific verb and resource ("Create a Google Ads link"), which cleanly separates it from ga4_delete_google_ads_link, ga4_update_google_ads_link, and the Search Ads 360 link creators. It does not explicitly call out those siblings, but the resource naming is precise enough for an agent to pick the right tool.

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?

It gives a hard precondition (GA4_MCP_ENABLE_WRITES=true and confirm=true), which tells the agent when the call is permitted. It does not say when to create a link versus update an existing one, nor what to do if a link already exists, so alternative-selection guidance is only implied by the sibling names.

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