AdCopilot

Google Ads: pause or resume account-level assets

set_customer_asset_status

DestructiveIdempotent

Pauses or re-enables assets linked at the account (customer) level.

An account-level asset serves on every eligible campaign. PAUSED stops
it serving account-wide; the asset and any campaign or ad group links
are untouched, and ENABLED switches it back on. It never deletes: status
REMOVED is refused. Use list_asset_links first to find the asset IDs and
field type.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    asset_ids: The asset IDs to change (or asset resource names). All must
        be linked at account level with the same field_type.
    field_type: The field type of the link, e.g. CALL, SITELINK, CALLOUT,
        STRUCTURED_SNIPPET, BUSINESS_NAME, BUSINESS_LOGO.
    status: PAUSED or ENABLED.

Returns:
    Dictionary with the updated customer asset link resource names.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations, it explains exactly what PAUSED does (stops serving account-wide), what survives (the asset and all campaign/ad group links are untouched), that ENABLED reverses it, and that REMOVED is rejected. That is precisely the impact-and-reversibility context an agent needs before invoking a destructiveHint=true mutation, and it is consistent with idempotentHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Front-loads the action and scope in the first sentence, then impact, then constraints, then parameters. The Args block repeats parameter names but is justified because the schema carries no descriptions; no sentence is filler.

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?

Covers scope, side effects, refused values, prerequisite discovery step, and all four required parameters, while the return value is already captured by the output schema. Nothing needed to invoke this mutation correctly and safely is missing.

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 all parameter meaning, and it does: customer_id format (numbers only, no hyphens), the cross-field constraint that all asset_ids must be account-level with the same field_type, field_type examples including CALL/SITELINK/CALLOUT, and the status enum PAUSED/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/re-enables) and a precisely scoped resource (assets linked at the account/customer level), then explains that such an asset serves on every eligible campaign. This scope statement cleanly distinguishes it from set_campaign_asset_status and set_ad_group_asset_status without needing to name them.

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 a concrete prerequisite ("Use list_asset_links first to find the asset IDs and field type") and a clear exclusion ("It never deletes: status REMOVED is refused"). It never explicitly names the campaign- or ad-group-level siblings as the alternative for non-account-level assets, so the routing rule is implied by scope rather than stated.

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?