Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_search_ads_360_link

Update a GA4 property's Search Ads 360 link to change data-sharing flags. Pass only the fields to change; the update mask is derived automatically, with an optional explicit mask for nested paths.

Instructions

[GA4 WRITE] Update a Search Ads 360 link (data-sharing flags via body). 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_search_ads_360_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRaw request-body object (JSON) merged OVER the typed fields — use for nested/advanced fields not exposed as flat args.
nameYesFull resource name of the Search Ads 360 link to target: "properties/{property}/searchAds360Links/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / body / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the Search Ads 360 link to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the Search Ads 360 link to target: \"properties/{property}/searchAds360Links/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/searchAds360Links\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares this is a WRITE, names the two gates required to apply it (env flag and confirm=true), and establishes partial-update semantics where unlisted fields are left alone. It does not state whether the operation is reversible or what a successful response contains, leaving a small gap.

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 compact sentences, front-loaded with the [GA4 WRITE] tag and the action, then the update semantics, then the prerequisites. No sentence is filler.

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 a nested body object and no output schema, it covers targeting, partial-update behavior, mask derivation, and write gating. Return values and failure modes are unaddressed, which is the only meaningful omission.

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 100%, so baseline is 3, but the description adds real meaning: it explains that body and flat fields are merged and that updateMask is auto-derived from the supplied fields, with explicit override needed for nested paths. That clarifies the interaction between the three non-confirm parameters in a way the schema alone does not.

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 ('Update a Search Ads 360 link') plus the scope of the change ('data-sharing flags via body'), which cleanly separates it from the create_/delete_ Search Ads 360 siblings whose verbs appear in the tool name.

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 usage rules: pass only the fields to change, let updateMask be derived, and override it only for nested paths. It also states the two preconditions (GA4_MCP_ENABLE_WRITES=true and confirm=true). It does not explicitly contrast with ga4_create_search_ads_360_link or the Google Ads link updater, so it stops short of full alternative routing.

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