AdCopilot

Google Ads: pause an auto-apply recommendation type

pause_auto_apply_subscription

DestructiveIdempotent

Pauses one auto-apply recommendation subscription.

Stops Google applying that type of recommendation to the account
unattended. It only pauses: it cannot enable, create or remove a
subscription. Pausing an already-paused subscription changes nothing. A
type the account has no subscription for is reported, not created. Only
the types in list_auto_apply_subscriptions' api_subscribable_types can be
paused here; the ui_only_types can only be changed in the Google Ads UI.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    recommendation_type: The subscription's type, as listed by
        list_auto_apply_subscriptions, e.g. SEARCH_PARTNERS_OPT_IN or
        USE_BROAD_MATCH_KEYWORD.

Returns:
    Dictionary with recommendation_type, previous_status, status,
    changed, message and the subscription's resource_name when one
    exists.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`customer_id`	Yes
`recommendation_type`	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.7/5.0

Behavior4/5

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

Adds substantial behavior beyond annotations: clarifies that it only pauses (no enable/create/remove), describes idempotency specifically ('pausing an already-paused subscription changes nothing'), and explains that missing subscriptions are reported not created. However, there is mild tension with destructiveHint=true since the tool explicitly cannot remove data, though pausing is still a mutation.

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?

Well-structured with clear Args and Returns sections, and front-loads the core purpose. Slightly verbose because the Returns section is redundant given the output schema exists, but overall efficient and all content is relevant.

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 the tool's complexity (mutation with type restrictions), the description covers purpose, usage constraints, edge cases, parameter semantics, and return values. Annotations cover the safety profile and output schema exists, so this is complete for correct invocation.

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 coverage is 0%, so the description must compensate. It provides crucial details: customer_id must be numbers only without hyphens; recommendation_type must come from list_auto_apply_subscriptions and includes examples (e.g., SEARCH_PARTNERS_OPT_IN). This fully documents both parameters beyond 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?

States a specific verb ('pauses') and resource ('auto-apply recommendation subscription'), and explicitly distinguishes itself from siblings by naming list_auto_apply_subscriptions and clarifying that it only pauses (cannot enable, create, or remove). An agent can identify its role 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: only types from list_auto_apply_subscriptions' api_subscribable_types can be paused; ui_only_types must be changed in the Google Ads UI. Also covers edge cases (already-paused changes nothing, no subscription reported not created). This leaves little ambiguity.

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?