Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_attribution_settings

Update a GA4 property's attribution settings: reporting model, conversion lookback windows, and Ads web-conversion export scope.

Instructions

[GA4 WRITE] Update a property's attribution: reporting model, acquisition/other conversion lookback windows, and the Ads web-conversion export scope. 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_update_attribution_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
reportingAttributionModelNo
adsWebConversionDataExportScopeNo
otherConversionEventLookbackWindowNo
acquisitionConversionEventLookbackWindowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0

TDQS

A3.7/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 burden and does contribute real value by flagging this as a write, naming the environment-flag gate, and requiring explicit confirmation. It omits the most consequential behavior for an update endpoint: whether omitted fields are left unchanged or reset, and whether the change is reversible or propagates to historical reporting.

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 sentences with no filler, front-loaded with the WRITE marker and the resource, followed immediately by the gating requirements. Every clause carries information an agent needs.

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 six-parameter mutation tool with no annotations and no output schema, the description covers purpose and prerequisites but leaves the update contract undefined (partial vs. full replacement, response contents). Adequate to invoke, insufficient to invoke confidently.

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 only 33% — property and confirm are documented, while the four enum parameters have no schema descriptions. The description partially compensates by naming those four settings in prose, but it adds no meaning about how the enum values differ or what happens when a setting is omitted, so the mapping from prose to parameters stays shallow.

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?

The description uses a specific verb and resource ("Update a property's attribution") and enumerates the exact settings touched: reporting model, acquisition/other conversion lookback windows, and Ads web-conversion export scope. That enumeration clearly separates it from adjacent siblings such as ga4_update_property or ga4_update_google_ads_link.

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 concrete precondition (GA4_MCP_ENABLE_WRITES=true and confirm=true), which tells the agent how to make the call succeed. It does not, however, say when this tool should be chosen over related configuration tools, nor any when-not conditions; usage is only implied by the name and the WRITE tag.

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