Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Create Microsoft Ads Promotion Extension

create_microsoft_promotion_extension

Add a time-bound promotional offer (sale, discount, promo code) that shows under a Microsoft Ads (Bing) 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, microsoft ads, bing, extension

            WHEN TO USE:
            - "Set up a Black Friday 20% off Microsoft Ads promotion for our Pro plan"
            - "Add a Bing holiday promo extension with code SUMMER2026"
            - "Register a Microsoft Ads sale: $50 off orders over $200"

            WHEN NOT TO USE:
            - Permanent pricing tiers (not a limited-time discount) → use create_microsoft_price_extension
            - Plain "Free Shipping" badge → use create_microsoft_callout_extension
            - Same promotion for Google Ads → use create_google_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_microsoft_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.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, correctly indicating a non-destructive write operation. The description elaborates on the behavior: it creates a time-bound offer with specific discount styles and qualifiers, and provides the exact date format. It doesn't mention potential side effects like limits on the number of active extensions or whether the extension attaches to all ads in a campaign, but the core behavior is clearly disclosed and consistent with the annotations.

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 it is well-organized with clear sections (ALSO KNOWN AS, KEYWORDS, WHEN TO USE, WHEN NOT TO USE, INPUTS, EXAMPLE) that aid scanning. While the KEYWORDS section is somewhat redundant for an agent, it doesn't detract from the core message. The main purpose is front-loaded, and the detailed parameter guidance is appropriately placed. It is verbose but justifiably so given the complexity.

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?

There is no output schema, but for a creation tool the return value is likely straightforward. The description covers all inputs, enum constraints, conditional parameters, date format, and provides a realistic example. It doesn't mention any prerequisites like having a Microsoft Ads account or connection, but these are implicit in the domain. Overall, an agent has enough information to call the tool correctly without external documentation.

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 only 55%, with some parameters (url, item) lacking descriptions in the schema. The description compensates by exhaustively listing every required and optional parameter, explaining the meaning of each enum value (e.g., category_type with MONETARY/PERCENT and their conditional requirements) and providing an example call. It adds significant semantic context that the schema alone does not provide.

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 Microsoft Ads (Bing) ad'. It clearly distinguishes itself from siblings via the 'WHEN NOT TO USE' section, naming create_microsoft_price_extension, create_microsoft_callout_extension, and create_google_promotion_extension as alternatives. An agent can immediately grasp what this tool does and how it differs from related tools.

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 includes dedicated 'WHEN TO USE' and 'WHEN NOT TO USE' sections with concrete examples and explicit alternative tool names. It states conditions like 'Permanent pricing tiers... use create_microsoft_price_extension' and 'Plain Free Shipping badge... use create_microsoft_callout_extension'. This leaves no ambiguity about when to select this tool over its siblings.

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