Skip to main content
Glama

AdCopilot

by cloud.adcopilot.mcp
OverviewDiscussionsAdmin

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. 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: 5c9bea8f.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
asset_idsYes
field_typeYes
ad_group_idYes
customer_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description explains exactly what PAUSED and ENABLED do, clarifies that the asset and its other links are untouched, and states that deletion is refused. This adds meaningful behavioral context for a mutating, idempotent tool.

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?

The description is front-loaded with the operation and key semantics, then uses compact Args and Returns sections. Every sentence adds useful information without repetition.

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?

Given five required parameters, no schema descriptions, and a mutating status-change operation, the description covers prerequisites, allowed values, side effects, refusal behavior, and return shape. An output schema exists, but the added return note is still concise and useful.

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 parameter meaning, and it does: customer_id format, ad group linkage, asset ID/resource-name support, required shared field_type, and allowed status values. This fully compensates for the bare schema.

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?

The description states a specific verb and resource: pauses or re-enables assets linked to one ad group. It distinguishes the scope from campaign-level, customer-level, and linking tools by emphasizing one ad group and status-only changes.

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 gives a clear prerequisite ('Use list_asset_links first') and a refusal condition ('status REMOVED is refused'), which helps the agent avoid misuse. However, it does not explicitly name sibling alternatives such as link_asset_to_ad_group or set_campaign_asset_status, so routing guidance is slightly incomplete.

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

All AdCopilot toolsInspect
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