AdCopilot

Google Ads: pause or resume ad group assets

set_ad_group_asset_status

DestructiveIdempotent

Pauses or re-enables assets linked to one ad group.

PAUSED stops the asset serving on this ad group's ads; the asset and its
other links are untouched, and ENABLED switches it back on, at once: it serves again and can spend. It never
deletes: status REMOVED is refused. Use list_asset_links first to find
the ad group, asset IDs and field type.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    ad_group_id: The ID of the ad group the assets are linked to.
    asset_ids: The asset IDs to change (or asset resource names). All must
        be linked to this ad group with the same field_type.
    field_type: The field type of the link, e.g. CALL, SITELINK, CALLOUT,
        STRUCTURED_SNIPPET, PRICE, AD_IMAGE.
    status: PAUSED or ENABLED.

Returns:
    Dictionary with the updated ad group asset link resource names.

Tools revision: d80f65c0.

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": {
      "customer_id": "<customer_id>",
      "ad_group_id": "<ad_group_id>",
      "asset_ids": "<asset_ids>",
      "field_type": "<field_type>",
      "status": "<status>"
    },
    "name": "set_ad_group_asset_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`asset_ids`	Yes
`field_type`	Yes
`ad_group_id`	Yes
`customer_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: PAUSED affects only this ad group's ads while other links are untouched, ENABLED makes the asset serve and spend again, and deletion is impossible because REMOVED is rejected — a useful nuance given destructiveHint=true. The gap is atomicity: with multiple asset_ids it is not stated whether a partial failure rolls back or leaves some links changed.

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 operation and its semantics, then a clean Args/Returns block. The opening paragraph is marred by an awkward mid-sentence insertion ('at once: it serves again and can spend') that interrupts the PAUSED/ENABLED contrast, but no sentence is truly wasted.

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 scope, prerequisites, the no-delete guarantee, and every parameter, and an output schema exists so the brief Returns note suffices. The remaining hole is failure behavior for a batch of asset_ids, which matters for a mutation that can affect several links at once.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the full burden, and it does: customer_id is numbers-only without hyphens, asset_ids accept IDs or resource names and must all share the same field_type link on this ad group, field_type enumerates concrete values (CALL, SITELINK, CALLOUT, STRUCTURED_SNIPPET, PRICE, AD_IMAGE), and status is constrained to PAUSED or ENABLED.

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 pair (pauses or re-enables) on a specific resource (assets linked to one ad group), and the 'one ad group' scoping distinguishes it from the sibling tools set_campaign_asset_status and set_customer_asset_status. An agent can identify the operation and its blast radius 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?

Gives an explicit prerequisite workflow: 'Use list_asset_links first to find the ad group, asset IDs and field type.' It also states a when-not constraint ('status REMOVED is refused'), but it never names the campaign- or customer-level sibling tools as alternatives for other scopes, leaving that routing to inference.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?