AdCopilot

Google Ads: pause or resume campaign assets

set_campaign_asset_status

DestructiveIdempotent

Pauses or re-enables assets linked to one campaign.

PAUSED stops the asset (a phone number, sitelink, callout...) serving on
this campaign'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 campaign, asset IDs and field type.

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

Returns:
    Dictionary with the updated campaign 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>",
      "campaign_id": "<campaign_id>",
      "asset_ids": "<asset_ids>",
      "field_type": "<field_type>",
      "status": "<status>"
    },
    "name": "set_campaign_asset_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`asset_ids`	Yes
`field_type`	Yes
`campaign_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.7/5.0

Behavior5/5

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

Beyond the annotations it explains what PAUSED actually does (stops the asset serving on this campaign's ads), that the asset and its other links survive, that ENABLED resumes serving and spending immediately, and that deletion via REMOVED is rejected. That clarifies the meaning of destructiveHint=true and idempotentHint=true in operational terms rather than restating them.

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?

The opening sentence front-loads the action, followed by effect/safety, then workflow, then Args. It is tight overall; the only redundancy is the short Returns line, which repeats what the existing output schema already declares.

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?

For a five-parameter mutation with zero schema coverage and an output schema, the description supplies the prerequisite lookup, the field-type coupling constraint, the legal status values, and the deletion refusal. Nothing an agent needs to invoke it correctly 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%, and the description compensates fully: it formats customer_id (numbers only, no hyphens), explains the shared field_type constraint across asset_ids, enumerates the accepted field_type values (CALL, SITELINK, CALLOUT, ...), and gives the two legal status values even though the schema declares no enum.

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?

"Pauses or re-enables assets linked to one campaign" gives a concrete verb pair and resource, and the phrase "linked to one campaign" scopes it away from the sibling variants set_ad_group_asset_status and set_customer_asset_status. An agent can pick this tool without opening any 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?

It states a concrete prerequisite workflow ("Use list_asset_links first to find the campaign, asset IDs and field type") and a firm exclusion (status REMOVED is refused), which is clear when-to-use guidance. It does not explicitly contrast with the ad-group or customer-level status tools, so the sibling choice is left partly implicit.

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?