Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_google_ads_link

Update the personalized advertising flag on a Google Ads link in GA4 by passing only the fields to change; requires write access and explicit confirmation.

Instructions

[GA4 WRITE] Update a Google Ads link (personalized advertising flag). Pass only the fields to change; updateMask is derived from them (override with an explicit updateMask for nested paths). 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": {
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_google_ads_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the Google Ads link to target: "properties/{property}/googleAdsLinks/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.
adsPersonalizationEnabledNo

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

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it labels the tool as a WRITE, discloses the two gating preconditions (environment flag and confirm), and explains that updateMask is auto-derived unless overridden. It stops short of saying whether the change is reversible or what an error/partial-update 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?

Three tight sentences plus a bracketed type tag, front-loaded with the operation and scope before the mask semantics and the auth preconditions. No filler, and each clause carries actionable information.

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 mutation tool with no annotations and no output schema, the description covers the critical unknowns: write gating, confirm requirement, and mask derivation. Only the post-call behavior (return value shape, failure modes) is left unaddressed, which is a minor residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds real meaning beyond it: it explains the derivation relationship between the supplied fields and updateMask, and flags the nested-path override case. The one gap is adsPersonalizationEnabled, which has no schema description and is only obliquely referenced via 'personalized advertising flag'.

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 (Update) and resource (Google Ads link), and narrows the scope with '(personalized advertising flag)'. The verb distinguishes it from the create/delete Google Ads link siblings, though it doesn't explicitly say how it differs from the parallel update tools such as ga4_update_search_ads_360_link.

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 concrete operational guidance: pass only the fields to change, override updateMask only for nested paths, and the call requires GA4_MCP_ENABLE_WRITES=true plus confirm=true. It does not state when to prefer an alternative tool or what happens when the write flag is off, but the context for correct invocation is clear.

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