Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_display_video_360_advertiser_link

Updates a Display & Video 360 advertiser link in GA4 to change ads personalization or campaign data sharing settings; send only modified fields and confirm the write.

Instructions

[GA4 WRITE] Update a DV360 advertiser link (ads personalization / campaign data sharing 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_display_video_360_advertiser_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 Display & Video 360 advertiser link to target: "properties/{property}/displayVideo360AdvertiserLinks/{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 Display & Video 360 advertiser link to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the Display & Video 360 advertiser link to target: \"properties/{property}/displayVideo360AdvertiserLinks/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/displayVideo360AdvertiserLinks\\/[A-Za-z0-9_-]+\\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?

With no annotations supplied, the description carries the full burden and does well: it discloses that this is a write gated behind an environment flag plus confirm=true, and explains that updateMask is auto-derived from the supplied fields rather than set by the agent. It does not describe failure modes or what the response contains, which keeps it out of 5 territory.

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, all front-loaded with the action and prerequisites first, then mechanics. No filler and no restatement of the schema's parameter text.

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 write tool with no annotations or output schema and a free-form nested body, this covers the critical unknowns: write gating, confirm requirement, and mask derivation. A brief note on which fields are valid for the body, or the failure behavior, would make it complete.

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 100%, so all four parameters are already documented, and the baseline is 3. The description does add genuine meaning for updateMask (auto-derived from passed fields, overrideable for nested paths), but the body/name semantics remain as the schema describes them.

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 DV360 advertiser link") and parenthesizes the domain it touches (ads personalization / campaign data sharing). The "[GA4 WRITE]" prefix and "Update" verb immediately separate it from the create/delete siblings in the catalog.

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 operating guidance: pass only the fields to change, the mask is derived automatically, and override it only for nested paths. It also names the two preconditions (GA4_MCP_ENABLE_WRITES=true and confirm=true) that must hold before a call can succeed. It does not explicitly contrast with the create/delete siblings, so it falls short of a full when/when-not statement.

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