Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.googleAdsLinks.patch

Updates a Google Ads link on a Google Analytics property via HTTP PATCH, applying only specified fields with an update mask. Use it to modify link settings; blocked in read-only safety profiles.

Instructions

Updates a GoogleAdsLink on a property [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON GoogleAnalyticsAdminV1betaGoogleAdsLink object accepting adsPersonalizationEnabled, canManageClients, createTime, creatorEmailAddress, customerId, name, updateTime; pass it via params or whole via body_file Siblings over the same resource: create, delete, list.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Identifier. Format: properties/{propertyId}/googleAdsLinks/{googleAdsLinkId} Note: googleAdsLinkId is not the Google Ads customer ID.
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaGoogleAdsLink object.
updateMaskNo[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., "field_to_update"). Omitted fields will not be updated. To replace the enti
request_bodyNoRequest body of type GoogleAnalyticsAdminV1betaGoogleAdsLink: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
nameNo
createTimeNo
customerIdNo
updateTimeNo
canManageClientsNo
creatorEmailAddressNo
adsPersonalizationEnabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body_file / description
      Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaGoogleAdsLink object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaGoogleAdsLink: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "adsPersonalizationEnabled": {
+      "type": "boolean"
+    },
+    "canManageClients": {
+      "type": "boolean"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "creatorEmailAddress": {
+      "type": "string"
+    },
+    "customerId": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Identifier. Format: properties/{propertyId}/googleAdsLinks/{googleAdsLinkId} Note: googleAdsLinkId is not the Google Ads customer ID."New value: +"[URL path segment] Identifier. Format: properties/{propertyId}/googleAdsLinks/{googleAdsLinkId} Note: googleAdsLinkId is not the Google Ads customer ID."
    • addedInput schema / properties / name / pattern
      Added value: +"^properties/[^/]+/googleAdsLinks/[^/]+$"
    • changedInput schema / properties / updateMask / description
      Previous value: -"Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"New value: +"[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"
    • addedInput schema / properties / updateMask / format
      Added value: +"google-fieldmask"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "adsPersonalizationEnabled": {
+      "type": "boolean"
+    },
+    "canManageClients": {
+      "type": "boolean"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "creatorEmailAddress": {
+      "type": "string"
+    },
+    "customerId": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden: it discloses the mutation, the read-only refusal behavior, and that the API's response resource is returned as JSON. It does not cover permission prerequisites or which fields are immutable, which keeps it short of 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.

Conciseness4/5

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

One dense, front-loaded sentence with em-dash separated clauses; every clause carries information (method, safety profile, return shape, body fields, siblings). Slightly over-packed but not padded.

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?

Covers mutation, safety-profile refusal, body composition, and return shape, and an output schema exists so return details need not be repeated. Missing are permission requirements and a note that updateMask governs which fields actually change, which matters for a PATCH tool with 7 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it enumerates the GoogleAnalyticsAdminV1betaGoogleAdsLink fields accepted in the request body and explains that the body may be supplied via `params` or wholesale via `body_file`. The crucial `updateMask` requirement is left to the schema rather than reinforced.

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?

States a specific verb and resource ('Updates a GoogleAdsLink on a property') plus the HTTP PATCH semantics, and explicitly lists the sibling operations over the same resource (create, delete, list) so an agent can differentiate without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the sibling alternatives and the constraint that the call is refused under --readonly safety profiles, which is genuine routing guidance. It does not explicitly state when a caller should prefer patch over re-creating the link, but for a patch operation that is largely implied.

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