Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

create_pmax_campaign

Draft a paused Performance Max campaign with its first asset group; require uploaded image assets and a target CPA to avoid impression loss.

Instructions

Draft a Performance Max campaign + first asset group — created PAUSED. time_zone defaults to EasternTimeUSCanada (US-centric default) — override for other markets. target_cpa is required by default (require_pmax_target_cpa setting, default true) — never create PMax without a target; removing one later explodes impressions (hard rule observed on a live Google Ads account). Set require_pmax_target_cpa false in advertiser settings to allow a no-target MaxConversions campaign instead. Images are REQUIRED (upload via upload_image_asset first). Each image_media_ids entry must already be in the account media library with MediaType Image1x1 or Image191x100; GenericImage, Image4x1, unknown types, and absent ids raise. Aborts the asset-group add if the campaign add fails. Returns a draft; apply with confirm_and_apply.

Live-verified 2026-07-30 — with an explicit target_cpa: campaign + asset group created and read back with both images carrying the correct per-image SubType; ImageAsset.Id = media id write-proven. NOT live-verified — the require_pmax_target_cpa=false / no-target_cpa path: only exercised against fakes, never run against the live API through this tool. NOT live-verified with non-default time_zone values.

On a mid-apply failure (asset group add raises after the campaign landed) the error carries every landed ID (campaign_ids) — reconcile account state before retrying (a retry re-runs ALL steps, including re-creating the campaign).

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>",
      "daily_budget": "<daily_budget>",
      "final_url": "<final_url>",
      "headlines": "<headlines>",
      "long_headlines": "<long_headlines>",
      "descriptions": "<descriptions>",
      "business_name": "<business_name>",
      "image_media_ids": "<image_media_ids>"
    },
    "name": "create_pmax_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
final_urlYes
headlinesYes
time_zoneNoEasternTimeUSCanada
target_cpaNo
daily_budgetYes
descriptionsYes
business_nameYes
long_headlinesYes
image_media_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the PAUSED creation state, the time_zone default, the target_cpa hard requirement with rationale, abort-on-failure semantics, and the critical non-idempotency warning that a retry after a mid-apply failure re-creates the campaign. It even scopes which paths are live-verified versus only tested against fakes.

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 core verb and PAUSED state are front-loaded, and most sentences carry operational value. The 'Live-verified 2026-07-30' block is longer than an agent needs and partially restates the target_cpa warning, costing some density.

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?

For a 10-parameter, 8-required mutation with no annotations and no output schema, the description covers ordering, prerequisites, failure reconciliation, and the returned draft well. It omits asset-count and character limits for headlines/long_headlines/descriptions, which are material PMax constraints an agent could easily violate.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate; it adds real meaning for time_zone, target_cpa, and image_media_ids (media-library membership plus MediaType restrictions). However, the eight other parameters — headlines, long_headlines, descriptions, daily_budget, business_name, name, final_url — get nothing beyond their names, leaving half the surface undocumented.

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 and resource — 'Draft a Performance Max campaign + first asset group — created PAUSED' — and immediately distinguishes the draft from the applied state ('apply with confirm_and_apply'). An agent knows exactly what is produced and in what state.

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

Usage Guidelines4/5

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

Gives clear prerequisites and alternatives: upload images via upload_image_asset first, override time_zone for non-US markets, and use the require_pmax_target_cpa=false path only when a no-target MaxConversions campaign is intended. It does not explicitly contrast itself with the sibling draft_campaign, leaving a small routing gap.

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