Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_display_video_360_advertiser_link

Creates a Display & Video 360 advertiser link for a GA4 property when writes are enabled and confirmation is provided.

Instructions

[GA4 WRITE] Create a Display & Video 360 advertiser 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>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_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.
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
advertiserIdNoDV360 advertiser id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / body / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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.8/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 disclose the write-gating mechanism (env flag plus confirm=true), which is the most important behavioral fact for an agent about to mutate state. It does not say what happens on an already-existing link, whether the operation is idempotent, or what permissions the DV360 advertiser requires, so it is not fully complete.

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: the action first, then the gating requirements. Every clause carries information an agent needs, with no filler or restatement of the tool name.

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 link-creation write with a fully documented four-parameter schema and no output schema, the description covers the action, the resource and the safety gate. The remaining gap is post-call expectations (duplicate-link behavior, error modes), which is minor but not nothing.

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%, so 'property', 'confirm', 'advertiserId' and the raw 'body' override are all already documented in the schema. The description adds no additional meaning about formats, precedence between body and flat fields, or ID expectations, so the baseline 3 applies.

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 Display & Video 360 advertiser link', and the '[GA4 WRITE]' tag marks it as a mutation. The verb 'Create' implicitly separates it from the delete/update DV360 siblings, though it never names them explicitly.

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 prerequisite (GA4_MCP_ENABLE_WRITES=true and confirm=true), which is useful pre-call guidance, but there is no statement about when to prefer this over ga4_update_display_video_360_advertiser_link or the Search Ads 360 / Google Ads link creators. Usage is implied by the verb rather than explained.

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