Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_search_ads_360_link

Creates a Search Ads 360 link for a specified GA4 property to connect advertising data; requires write access enabled and confirm=true.

Instructions

[GA4 WRITE] Create a Search Ads 360 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_search_ads_360_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".
advertiserIdNo

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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: this is a mutation ('[GA4 WRITE]', 'Create') gated behind an environment flag and an explicit confirm=true. However, it says nothing about duplicate-handling or idempotency, what side effects creating a link has, whether an existing link is replaced, or what permissions beyond the write flag are needed. The WRITE tag and gating disclosure are genuine value; the mutation-effect detail is absent.

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 the WRITE classification and the required gating flags front-loaded. There is no filler, and the conditions an agent must satisfy before calling are placed before anything else.

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 write tool with no annotations and no output schema, the description covers the critical gate (write enablement plus confirm) but leaves out the effect of the operation, the meaning of advertiserId, and how the nested body object is merged. There is no output schema, so return values need not be explained, but the mutation semantics and one parameter remain unexplained.

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 75% and the schema already describes property, confirm, and body. The description only echoes confirm=true and implies property targeting; it adds no meaning for advertiserId (entirely undocumented in both places) or for how the raw body object interacts with the typed fields. This is the baseline 3 for a high-coverage schema, not a compensated gap.

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 Search Ads 360 link.' That is clearly distinct from the delete/update SA360 siblings and from the Google Ads / Display & Video link creators, so an agent can identify the correct operation without opening the schema. It stops short of an explicit contrast statement against siblings, hence 4 rather than 5.

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 only implied through the verb and the gating prerequisites ('Requires GA4_MCP_ENABLE_WRITES=true and confirm=true'). There is no explicit guidance on when to choose this over the update tool for an existing link, no note about preconditions (existing SA360 advertiser, permissions), and no stated alternatives. The prerequisite note is useful but is not when-to-use guidance.

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