AdCopilot

Google Ads: create promotion asset

create_promotion_asset

Creates a promotion asset that can be linked to campaigns or ad groups.

Promotion assets highlight sales and special offers in your ads.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    promotion_target: What the promotion is for (e.g., "Summer Collection", "All Shoes").
    final_url: The page the promotion sends clicks to: the business's
        real landing page for this offer. Required.
    discount_modifier: One of: NONE, UP_TO. Default: NONE.
    percent_off: Percentage discount (e.g., 20 for 20% off). Use this OR money_amount_off.
    money_amount_off_micros: Money discount in micros of money_amount_off_currency (5000000 = 5.00 off). Use this OR percent_off.
    money_amount_off_currency: Currency code for money discount; use the account's currency (e.g., "INR", "USD").
    occasion: Occasion for the promotion. One of: NONE, NEW_YEARS, VALENTINES_DAY,
        EASTER, MOTHERS_DAY, FATHERS_DAY, LABOR_DAY, BACK_TO_SCHOOL, HALLOWEEN,
        BLACK_FRIDAY, CYBER_MONDAY, CHRISTMAS, BOXING_DAY, and more. Default: NONE.
    language_code: Language code (e.g., "en"). Default: "en".
    start_date: Asset start date in YYYY-MM-DD format. Optional.
    end_date: Asset end date in YYYY-MM-DD format. Optional.
    redemption_start_date: Promotion redemption start date in YYYY-MM-DD format. Optional.
    redemption_end_date: Promotion redemption end date in YYYY-MM-DD format. Optional.
    promotion_code: A promotion code users can use (e.g., "SAVE20"). Optional.

Returns:
    Dictionary with the created asset resource name.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Default
`end_date`	No
`occasion`	No	NONE
`final_url`	Yes
`start_date`	No
`customer_id`	Yes
`percent_off`	No
`language_code`	No	en
`promotion_code`	No
`promotion_target`	Yes
`discount_modifier`	No	NONE
`redemption_end_date`	No
`redemption_start_date`	No
`money_amount_off_micros`	No
`money_amount_off_currency`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The annotations already declare that this is a non-read-only, non-destructive, non-idempotent creation operation. The description adds that the resulting asset can be linked to campaigns or ad groups and returns a resource name, but it does not discuss permissions, side effects, duplicate creation behavior, or linking requirements beyond that brief mention.

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 long but appropriately so for a 14-parameter creation tool. It is front-loaded with the core action and asset explanation, then organizes parameter details cleanly under Args and Returns with no meaningful filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and annotations, the description covers nearly everything needed to invoke the tool correctly, especially the full parameter semantics. The only notable gap is that it does not explain the subsequent linking lifecycle in detail, despite mentioning that the asset can be linked.

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 carries the full burden and does so thoroughly. It documents all 14 parameters, including formats, defaults, enum values, the percent_off versus money_amount_off_micros choice, micros conversion, currency expectations, and date formats.

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 gives a specific verb and resource: it creates a promotion asset. It also explains that promotion assets highlight sales and special offers, which distinguishes this asset type from the many other create_*_asset siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies the tool is for sales and special-offer promotions, but it does not explicitly say when to choose this over alternatives such as create_price_asset, create_callout_asset, or create_sitelink_asset. It also does not mention prerequisites beyond the required landing page.

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?