Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_display_video_360_advertiser_link

Deletes a Display & Video 360 advertiser link from a GA4 property. Requires deletes enabled and confirm set to true, ensuring the link is removed only with explicit per-call confirmation.

Instructions

[GA4 DELETE] Delete a DV360 advertiser link. Requires GA4_MCP_ENABLE_DELETES=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_delete_display_video_360_advertiser_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the Display & Video 360 advertiser link to target: "properties/{property}/displayVideo360AdvertiserLinks/{id}".
confirmYesMust be true to delete.

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 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

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it usefully discloses an environment-level enablement flag and a confirmation requirement that an agent could not otherwise infer. However, it never states that the deletion is irreversible, whether dependent configurations are affected, or what the response contains, which are the key behavioral facts for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the destructive verb and the gating requirements front-loaded; nothing is padded. The bracketed tag is slightly redundant with the tool name but serves as a fast scan cue across a large delete-heavy sibling set.

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 two-parameter destructive tool with full schema coverage and no output schema, the description covers the invocation gate but omits consequence information (irreversibility, scope of what is removed). An agent could call it correctly but not fully reason about the risk.

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 both the resource-name pattern and the confirm boolean are fully documented in the schema; the description's mention of confirm=true merely restates that. It adds no extra meaning about the name format or the confirm semantics, so the baseline of 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 gives a specific verb and resource ("Delete a DV360 advertiser link") plus a bracketed [GA4 DELETE] tag, so an agent can immediately distinguish it from the create/update display_video_360_advertiser_link siblings. It stops short of naming those alternatives explicitly, but the verb alone makes the operation unambiguous.

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 states the two preconditions for invocation (GA4_MCP_ENABLE_DELETES=true and confirm=true), which is real when-to-use guidance in the form of a gate. It does not say when to prefer this over related tools or what happens if the flag is unset beyond implying failure, so guidance is adequate but not complete.

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