Skip to main content
Glama
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

Draft a sitelink edit

update_sitelink

Preview in-place edits to a Google Ads sitelink, changing only passed fields while preserving its ID and performance history. Validates new landing URLs and locks current values for safe apply.

Instructions

Draft changing a sitelink asset in place — returns a PREVIEW.

Only the fields passed change; empty fields stay as they are. The asset keeps its ID and performance history everywhere it is linked. A new final_url is checked for reachability. The preview pins the current values; an edit in Google Ads before the apply stops it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": {
      "asset_id": "<asset_id>"
    },
    "name": "update_sitelink"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYesNumeric ID of the sitelink asset.
end_dateNoLast day the sitelink shows, YYYY-MM-DD. Empty keeps it.
final_urlNoNew landing page URL; must be reachable.
link_textNoNew link text, at most 25 characters.
start_dateNoFirst day the sitelink shows, YYYY-MM-DD. Empty keeps it.
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
clear_fieldsNo"start_date" and/or "end_date" to remove that date.
description1NoNew first description line, at most 35 characters.
description2NoNew second description line, at most 35 characters. Google needs both description lines or neither.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.45.0
    • addedInput schema / properties / clear_fields
      Added value: +{
      +  "default": [],
      +  "description": "\"start_date\" and/or \"end_date\" to remove that date.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / end_date
      Added value: +{
      +  "default": "",
      +  "description": "Last day the sitelink shows, YYYY-MM-DD. Empty keeps it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / start_date
      Added value: +{
      +  "default": "",
      +  "description": "First day the sitelink shows, YYYY-MM-DD. Empty keeps it.",
      +  "type": "string"
      +}
  2. Addedv0.35.1

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which only say readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the key behaviors: partial-update semantics ('only the fields passed change'), identity/history preservation ('keeps its ID and performance history everywhere it is linked'), a validation step for final_url, and the concurrency guard that an out-of-band Google Ads edit invalidates the pinned preview. It also makes clear the call does not apply the change, which resolves the ambiguity left by a non-destructive mutation hint.

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?

Front-loaded with the core action and its PREVIEW nature in the first clause, followed by tightly ordered behavioral facts. The trailing 'Google Ads API: <link>' line adds little for an agent that is already inside a Google Ads toolset and could be dropped, but the rest is dense and waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. The description covers what an agent needs to call this correctly for a 9-parameter mutation: what changes, what is preserved, what is validated, and the fact that the result is only a preview subject to invalidation.

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%, so the schema already documents each parameter, including the empty-string-keeps behavior and the paired description lines. The description reinforces the partial-update rule at a general level but adds no new per-parameter detail, so the baseline for full schema coverage 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 first sentence pairs a specific verb and resource ('Draft changing a sitelink asset in place') and immediately qualifies it with 'returns a PREVIEW', so an agent knows this is a staging step rather than an applied mutation. It does not name a sibling alternative, so it falls short of full sibling differentiation.

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 rather than stated: the preview/pin-concurrency notes hint that this is the precursor to some apply step, but the description never says when to choose this over a create or delete sitelink tool, nor does it state prerequisites such as which account or permission level is needed. The agent can infer the scenario but is given no explicit routing rule.

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