Skip to main content
Glama

publish_campaign_to_microsoft_ads

Publish a complete Search Campaign (Campaign, Ad Groups, Keywords, Responsive Search Ads, and Negative Keywords) directly to Microsoft Advertising (Bing Ads) with Status=Paused. Requires confirm=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "dailyBudget": "<dailyBudget>",
      "finalUrl": "<finalUrl>",
      "adGroups": "<adGroups>",
      "confirm": "<confirm>"
    },
    "name": "publish_campaign_to_microsoft_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmYesMust be true to execute creation in Microsoft Advertising.
adGroupsYes
finalUrlYes
accountIdNo
customerIdNo
dailyBudgetYes
languageCodeNo2-letter target language code (e.g. 'en', 'de', 'fr', 'es').
negativeKeywordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / languageCode
      Added value: +{
      +  "description": "2-letter target language code (e.g. 'en', 'de', 'fr', 'es').",
      +  "type": "string"
      +}
  2. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / adGroups
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "descriptions": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "headlines": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "keywords": {
      +        "items": {
      +          "properties": {
      +            "matchType": {
      +              "enum": [
      +                "BROAD",
      +                "PHRASE",
      +                "EXACT"
      +              ],
      +              "type": "string"
      +            },
      +            "text": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "text"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "path1": {
      +        "type": "string"
      +      },
      +      "path2": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "headlines",
      +      "descriptions",
      +      "keywords"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / confirm / default
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually publish to Microsoft Advertising"New value: +"Must be true to execute creation in Microsoft Advertising."
    • addedInput schema / properties / customerId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dailyBudget
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / draftId
      Removed value: -{
      -  "description": "The draftId returned by save_campaign_draft or generate_campaign_draft",
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
    • addedInput schema / properties / finalUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / negativeKeywords
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "draftId"
      -]New value: +[
      +  "name",
      +  "dailyBudget",
      +  "finalUrl",
      +  "adGroups",
      +  "confirm"
      +]
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two valuable behaviors: the campaign is created Paused rather than live, and a confirm=true gate must be passed. It omits other important behavior for a write operation — required permissions/auth, what happens on partial failure of nested ad groups, idempotency, and rate limits.

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?

A single front-loaded sentence names the verb and resource first, followed by the confirm requirement as a short standalone clause. Nearly every word earns its place, with only mild redundancy between the parenthetical component list and the title-style enumeration.

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

Completeness2/5

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

This is a high-complexity mutation tool with 9 parameters, deeply nested ad group objects, no annotations and no output schema. The description says nothing about what is returned (campaign IDs, per-ad-group results), error semantics, or how the account/customer identifiers are resolved, which is too thin for an operation of this weight.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 22% across 9 parameters, so the description needs to compensate and largely does not. It maps the payload hierarchy (ad groups, keywords, RSAs, negative keywords) but adds nothing about dailyBudget units/currency, finalUrl, name constraints, or the accountId/customerId targeting parameters that determine which account receives the campaign.

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?

States a specific verb ('Publish') and a precisely scoped resource ('complete Search Campaign: Campaign, Ad Groups, Keywords, Responsive Search Ads, Negative Keywords') targeted at Microsoft Advertising. The explicit platform naming cleanly separates it from the sibling publish_campaign_to_google_ads.

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 when to use it by naming the destination platform and noting the campaign is created with Status=Paused, plus a hard precondition of confirm=true. It never states when NOT to use it, nor does it point at siblings like set_microsoft_campaign_status or list_microsoft_ads_campaigns for post-creation steps, leaving the agent to infer the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources