Skip to main content
Glama

Update ad group

update_ad_group

Partial update of an ad group. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

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": {
      "ad_group_id": "<ad_group_id>",
      "body": "<body>"
    },
    "name": "update_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body matching the AdGroupUpdate schema. Fields below; see the OpenAPI spec for nested object shapes.
space_idNoOverride the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.
ad_group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / properties / platform
      Added value: +{
      +  "description": "Fixed after creation: sending a different platform is refused (400 AD_GROUP_PLATFORM_IMMUTABLE). Use copy_ad_group instead.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / body / properties / _native
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Platform-only settings, keyed by platform id (for example {\"openai-ads\": {\"budgetKind\": \"LIFETIME\"}}). Each value is stored and returned as sent. The NativeExtensions schema in the OpenAPI spec lists every key each platform reads and where (campaign, ad group or ad) — a lifetime budget, a bidding type, delivery surfaces, the words and image on a card. On update, send the whole object for a platform: it replaces that platform's settings.",
      +  "type": "object"
      +}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare non-read-only and non-destructive, so the description usefully adds that updates are partial and that the full object is returned. It omits other behavioral traits an agent would want: whether omitted fields are untouched, that _native objects are wholesale-replaced per platform, and the platform-immutability refusal (both buried in the schema rather than surfaced).

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?

Three compact sentences, front-loaded with the operation and return shape, followed by the scoping caveat. No filler. Minor cost: the "updated/created" phrasing muddies an otherwise crisp statement.

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?

With no output schema, the description correctly compensates by stating that the full object is returned. But for a mutation tool with nested body objects and 67% parameter coverage, it leaves out the immutability constraint and the replace-not-merge behavior of _native settings, which materially affect how an agent should call it.

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 67% with nested objects, and the description adds little field-level meaning beyond restating that space_id overrides the session binding for one call. The nuanced semantics (platform fixed at creation, _native replacement behavior) live in the schema descriptions, not the tool description. Baseline 3 fits.

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?

"Partial update of an ad group" gives a specific verb and resource, and the word "partial" distinguishes it from a full-replace operation. The return statement clarifies what comes back, though "updated/created" introduces ambiguity about whether the call can create an ad group. No sibling is named as a contrast case.

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 description explicitly covers the Space-scoping decision: use set_active_space to switch, or pass space_id for a one-off override. That is genuine when-to-use guidance. However, it says nothing about when to prefer copy_ad_group (relevant given platform immutability) or when update is inappropriate versus create_ad_group/delete_ad_group.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources