Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Draft campaign changes

update_campaign

Update an existing Google Ads campaign's settings like bidding strategy, budget, and targeting. Returns a preview to confirm via confirm_and_apply before changes are applied.

Instructions

Draft an update to an existing campaign — returns a PREVIEW, does NOT apply.

Only include the parameters you want to change. Omit the rest.

campaign_id: the numeric ID of the campaign to update (required) bidding_strategy: MAXIMIZE_CONVERSIONS | TARGET_CPA | TARGET_ROAS | MAXIMIZE_CONVERSION_VALUE | TARGET_SPEND | MANUAL_CPC target_cpa: required if bidding_strategy is TARGET_CPA (in account currency) target_roas: required if bidding_strategy is TARGET_ROAS daily_budget: new daily budget in account currency geo_target_ids: REPLACES all geo targets. Common IDs: "2276" Germany, "2040" Austria, "2756" Switzerland, "2840" USA, "2826" UK language_ids: REPLACES all language targets. Common IDs: "1001" German, "1000" English, "1002" French, "1004" Spanish search_partners_enabled: include ads on Search partners display_network_enabled: enable Search campaign display expansion display_expansion_enabled: alias for display_network_enabled max_cpc: Maximize Clicks CPC cap when bidding_strategy is TARGET_SPEND, or when the existing campaign already uses TARGET_SPEND

Call confirm_and_apply with the returned plan_id to execute.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`max_cpc`	No
`target_cpa`	No
`campaign_id`	Yes
`customer_id`	No
`target_roas`	No
`daily_budget`	No
`language_ids`	No
`geo_target_ids`	No
`bidding_strategy`	No
`display_network_enabled`	No
`search_partners_enabled`	No
`display_expansion_enabled`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Jun 19, 2026

TDQS

A5/5.0

Behavior5/5

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

The annotation readOnlyHint=false and destructiveHint=false are consistent with the description's statement that it returns a preview and does not apply changes. The description adds important behavioral context by specifying the preview nature and the requirement to call confirm_and_apply.

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 well-organized, listing each parameter with its meaning in a compact bullet-like format. It avoids redundancy and each sentence serves a purpose, including the final instruction to confirm.

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 (conditional requirements, aliases, cross-reference to confirm_and_apply), the description covers all necessary context. It does not need to describe output schema since the preview behavior and execution path are clearly stated.

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?

The schema provides no descriptions (0% coverage), but the tool description compensates fully. It explains conditional requirements (e.g., target_cpa required for TARGET_CPA), aliases (display_expansion_enabled for display_network_enabled), and special cases (max_cpc only for TARGET_SPEND or when existing campaign uses it).

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 verb 'draft' clearly indicates a preview action, and the resource is 'campaign'. It explicitly says 'returns a PREVIEW, does NOT apply', and the sibling tools include draft_campaign (for new campaigns) and confirm_and_apply (to execute), making the distinction clear.

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?

The description explicitly states 'Only include the parameters you want to change. Omit the rest.' and 'Call confirm_and_apply with the returned plan_id to execute.' This provides clear guidance on when to use this tool versus alternatives.

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

Deploy Server