Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_add_promotion_extension

Add a promotion extension to a Google Ads campaign to highlight special offers, sales, or discounts with a prominent visual treatment in ads.

Instructions

Add promotion extension to a campaign.

Promotion extensions highlight special offers, sales, and discounts with a prominent visual treatment in your ads.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) campaign_id: Campaign ID to add promotion promotion_target: What's being promoted (e.g., "Summer Sale") occasion: Occasion (UNKNOWN, NEW_YEARS, VALENTINES_DAY, MOTHERS_DAY, FATHERS_DAY, LABOR_DAY, BACK_TO_SCHOOL, HALLOWEEN, BLACK_FRIDAY, CYBER_MONDAY, CHRISTMAS, BOXING_DAY, INDEPENDENCE_DAY) discount_modifier: Modifier (NONE, UP_TO) money_amount_off: Dollar amount off (e.g., 25.00 for $25 off) percent_off: Percent off (e.g., 20 for 20% off) promotion_code: Optional promo code text

Returns: Promotion extension creation result

Example: google_ads_add_promotion_extension( customer_id="1234567890", campaign_id="12345678", promotion_target="Holiday Sale", occasion="CHRISTMAS", percent_off=25, promotion_code="HOLIDAY25" )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaign_idYes
promotion_targetYes
occasionNoUNKNOWN
discount_modifierNoNONE
money_amount_offNo
percent_offNo
promotion_codeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must disclose behaviors. It only states the action ('add') without mentioning idempotency, error conditions, permissions, or side effects (e.g., whether existing promotions are overridden).

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?

Well-structured with a one-line summary, purpose paragraph, parameter list, returns line, and an example. Every sentence is informative, no fluff. The example is particularly helpful.

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?

Covers purpose, parameters, and returns (via example). Lacks behavioral details but includes an output schema (signal true). For a tool with 8 parameters, it is fairly complete, though usage guidance 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%, but the description provides detailed explanations for each parameter (e.g., customer_id format, occasion enum values, discount_modifier options). This fully compensates for the schema gap, adding significant meaning.

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 clearly states the tool adds a promotion extension to a campaign, specifying the action and resource. It distinguishes from siblings by naming the specific extension type 'promotion extension' and explains its purpose (highlighting special offers).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this vs. other extension tools like add_call_extension or add_callout_extension. The description implies it's for promotions but does not specify conditions or alternatives, leaving the agent to infer.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnoconnor0/google-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server