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

AdLoop: Google Ads, Reddit Ads & GA4

Draft a callout edit

update_callout

Draft a preview of changes to a callout asset in place; only the fields you pass change while the asset keeps its ID and performance history. Nothing is sent if the asset was edited first.

Instructions

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

Only what is passed changes. The asset keeps its ID and performance history, and the change shows everywhere it is linked. The preview pins the current values; if someone edits the asset in Google Ads before the apply, nothing is sent.

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_callout"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYesNumeric ID of the callout asset.
end_dateNoLast day the callout shows, YYYY-MM-DD. Empty keeps it.
start_dateNoFirst day the callout shows, YYYY-MM-DD. Empty keeps it.
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
callout_textNoThe new text, at most 25 characters. Empty keeps it.
clear_fieldsNo"start_date" and/or "end_date" to remove that date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.45.0
    • addedInput schema / properties / callout_text / default
      Added value: +""
    • changedInput schema / properties / callout_text / description
      Previous value: -"The new text, at most 25 characters."New value: +"The new text, at most 25 characters. Empty keeps it."
    • 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 callout shows, YYYY-MM-DD. Empty keeps it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / start_date
      Added value: +{
      +  "default": "",
      +  "description": "First day the callout shows, YYYY-MM-DD. Empty keeps it.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "asset_id",
      -  "callout_text"
      -]New value: +[
      +  "asset_id"
      +]
  2. Addedv0.35.1

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations by describing partial-update semantics ('Only what is passed changes'), identity and history preservation ('keeps its ID and performance history'), propagation ('shows everywhere it is linked'), and an optimistic-concurrency guard ('The preview pins the current values; if someone edits the asset in Google Ads before the apply, nothing is sent'). These are exactly the mutation behaviors an agent cannot infer from destructiveHint:false.

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-loads purpose and preview behavior in the first sentence, then layers mutation semantics and the staleness caveat efficiently. The closing Google Ads API URL is reference filler that adds little, and the hard line breaks make it slightly choppier than needed, but there is no redundant prose.

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 6-parameter draft tool with annotations and an output schema, the description covers the important unknowns: that the return is a preview, that the update is partial and non-destructive to identity, and that the preview can go stale. Only the relationship to the subsequent apply step (which tool consumes the preview) is left implicit.

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?

With 100% schema description coverage, the schema already documents every parameter including the 'Empty keeps it' defaults and clear_fields. The description reinforces the partial-update intent but adds no parameter-level detail such as how clear_fields interacts with empty start_date/end_date, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Draft changing a callout asset in place') and clarifies the mode of operation ('returns a PREVIEW'), which separates it from a plain create tool like draft_callouts. It stops short of naming a sibling or explicitly contrasting create-vs-update, so an agent must infer that from 'changing'.

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?

The preview/staleness note implies this is a two-step draft-then-apply workflow and conveys when the draft becomes stale, which is useful context. However, it never names the apply tool or states when to use this versus a sibling such as draft_callouts or update_call_asset; usage is implied rather than prescribed.

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