Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Create Google Ads Promotion Extension

create_google_promotion_extension

Add a time-bound promotional offer (sale, discount, promo code) that shows under a Google Ads ad — flag a holiday occasion, pick the discount style (% off or $ off), optionally attach a promo code or "on orders over $X" qualifier, and set the start/end window. Standard for Black Friday, Cyber Monday, seasonal sales, flash discounts, holiday campaigns.

            ALSO KNOWN AS: promotion, promo, discount, sale, offer, coupon, promo code, voucher, deal, holiday sale, seasonal offer

            KEYWORDS: promotion, promo, promo code, coupon, sale, discount, offer, deal, black friday, cyber monday, holiday, christmas, summer sale, percent off, dollar off, $ off, voucher, google ads, extension

            WHEN TO USE:
            - "Set up a Black Friday 20% off promotion for our Pro plan"
            - "Add a holiday promo extension with code SUMMER2026"
            - "Register a sale: $50 off orders over $200"
            - "Create a Cyber Monday discount extension running Nov 30 to Dec 2"

            WHEN NOT TO USE:
            - Permanent pricing tiers (not a limited-time discount) → use create_google_price_extension
            - Plain "Free Shipping" badge → use create_google_callout_extension
            - Lead-capture form attached to the ad → use create_google_lead_form_extension
            - Same promotion for Microsoft Ads / Bing → use create_microsoft_promotion_extension

            INPUTS (required):
            - occasion: holiday/event tag (NONE if no specific occasion). Available: NONE, BACK_TO_SCHOOL, BLACK_FRIDAY, BOXING_DAY, CARNIVAL, CHINESE_NEW_YEAR, CHRISTMAS, CYBER_MONDAY, DIWALI, EASTER, EID_AL_ADHA, EID_AL_FITR, END_OF_SEASON, EPIPHANY, FALL_SALE, FATHERS_DAY, HALLOWEEN, HANUKKAH, HOLI, INDEPENDENCE_DAY, LABOR_DAY, MOTHERS_DAY, NATIONAL_DAY, NAVRATRI, NEW_YEARS, PARENTS_DAY, PASSOVER, RAMADAN, ROSH_HASHANAH, SINGLES_DAY, SONGKRAN, SPRING_SALE, ST_NICHOLAS_DAY, SUMMER_SALE, VALENTINES_DAY, WINTER_SALE, WOMENS_DAY, YEAR_END_GIFT.
            - url: landing page for the promotion.
            - item: what's on sale (1-20 chars). E.g. "Pro subscription".
            - category_type: discount style.
                * MONETARY        → "$X off". Provide category_amount.
                * UP_TO_MONETARY  → "Up to $X off". Provide category_amount.
                * PERCENT         → "X% off". Provide category_percent (≤100).
                * UP_TO_PERCENT   → "Up to X% off". Provide category_percent (≤100).
            - details_type: optional qualifier.
                * NONE            → no qualifier.
                * ON_ORDERS_OVER  → "on orders over $X". Provide details_amount.
                * PROMO_CODE      → "with code XXXX". Provide details_promo_code (≤15 chars).
            - start_date / end_date: ISO-8601 in pattern "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'" (e.g. 2026-11-25T00:00:00.000Z). Both must be today or in the future.

            INPUTS (optional, see category_type / details_type above):
            - category_amount, category_percent, details_promo_code, details_amount.

            EXAMPLE — Black Friday 20% off Pro with promo code:
            create_google_promotion_extension(
                occasion="BLACK_FRIDAY",
                url="https://example.com/sale",
                item="Pro subscription",
                category_type="PERCENT",   category_percent=20,
                details_type="PROMO_CODE", details_promo_code="BF2026",
                start_date="2026-11-25T00:00:00.000Z",
                end_date="2026-11-30T23:59:59.000Z",
            )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
itemYes
end_dateYesISO-8601 "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'". Future or present.
occasionYes
start_dateYesISO-8601 "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'". Future or present.
details_typeYes
category_typeYes
details_amountNoThreshold USD amount; supply when details_type is ON_ORDERS_OVER.
category_amountNoUSD amount; supply when category_type is MONETARY or UP_TO_MONETARY.
category_percentNoPercent (≤100); supply when category_type is PERCENT or UP_TO_PERCENT.
details_promo_codeNoPromo code; supply when details_type is PROMO_CODE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=false, so the description doesn't need to establish that this is a non-destructive write operation. Beyond that, it adds useful behavioral context: the offer is time-bound, must have start/end dates in the present or future, and attaches to a Google Ads ad. It stops short of describing post-creation effects or any auth/rate-limit caveats, but the core behavior is clear.

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?

The description is long but well-structured with clear headers (ALSO KNOWN AS, KEYWORDS, WHEN TO USE, WHEN NOT TO USE, INPUTS, EXAMPLE). The keyword lists and usage examples earn their place for agent semantic matching, and the example is valuable for a complex conditional parameter set. It is verbose, but every section contributes.

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?

Despite having 11 parameters, 7 required fields, no output schema, and conditional logic between category_type and category_amount/category_percent, the description explains every call-relevant aspect: optional parameters, constraints, enum values, date format, and a full runnable example. An agent has everything needed to invoke the tool correctly.

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?

With schema coverage at only 55%, the description takes on the full burden of explaining the parameters. It defines url as 'landing page for the promotion,' explains item as 'what's on sale (1-20 chars),' maps each category_type to its required amount/percent field, explains details_type qualifiers, and gives the exact ISO-8601 pattern with an example. The included worked example ties everything together.

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 opens with a specific verb and resource: 'Add a time-bound promotional offer... that shows under a Google Ads ad.' It clearly identifies the tool's exact purpose—creating a promotion extension for Google Ads—and distinguishes it from sibling tools in the WHEN NOT TO USE section by naming create_google_price_extension, create_google_callout_extension, and others.

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 provides explicit WHEN TO USE examples ('Set up a Black Friday 20% off promotion') and an explicit WHEN NOT TO USE list with alternative tools for each excluded scenario, such as permanent pricing tiers → create_google_price_extension and lead-capture forms → create_google_lead_form_extension. This is exactly the level of routing guidance an agent needs.

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

All Metadata MCP Connector 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