Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_rollup_property_source_link

Remove a source property from a GA4 rollup (360) by targeting its rollupPropertySourceLinks resource name; requires deletes enabled and confirm=true.

Instructions

[GA4 DELETE] Remove a source property from a rollup (360). 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_rollup_property_source_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the rollup property source link to target: "properties/{property}/rollupPropertySourceLinks/{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 rollup property source link to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the rollup property source link to target: \"properties/{property}/rollupPropertySourceLinks/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/rollupPropertySourceLinks\\/[A-Za-z0-9_-]+\\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 two safety gates that govern whether the call succeeds: the GA4_MCP_ENABLE_DELETES environment flag and confirm=true. That is exactly the kind of operational prerequisite an agent otherwise cannot know. It stops short of disclosing irreversibility, side effects on reporting, or what a successful response returns, which keeps it from a 5.

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 with no filler: the action and scope come first, the gating conditions second. The bracketed [GA4 DELETE] prefix front-loads the destructive classification, and every clause earns its place.

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 two-parameter destructive call with no output schema and no annotations, the definition covers purpose, preconditions, and the confirmation requirement. The remaining gap is behavioral consequence (irreversibility, effect on rollup data), which matters somewhat for a delete but is not strictly needed to invoke it correctly.

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%, and both parameters (name, confirm) are fully documented in the schema, including the resource-name pattern. The description only restates confirm=true, adding no format or targeting detail beyond the schema, 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: 'Remove a source property from a rollup (360)', prefixed with the [GA4 DELETE] tag, which cleanly separates it from the ga4_create_rollup_property_source_link sibling. It could be sharper about the rollup-vs-source relationship, but an agent can tell exactly what is being removed and from where.

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?

Usage is implied by 'Remove a source property from a rollup' plus the stated prerequisites (GA4_MCP_ENABLE_DELETES=true and confirm=true), which function as hard gating conditions. There is no explicit statement of when to choose this over the other delete/link tools or when not to use it, so guidance remains implicit beyond the gating flags.

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