Microsoft Advertising MCP server

Overview Schema Source Related Servers Discussions Admin

bing list ad creatives

bing_list_ad_creatives

Read-onlyIdempotent

Lists image assets linked to ads and Performance Max asset groups with their parent IDs and names, so you can audit creative inventory in Microsoft Advertising accounts.

Instructions

List image assets linked to account-owned ads and Performance Max asset groups, with parent IDs and names. Bounded scan; no inferred delivery, video contents or KPI attribution.

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": {
      "accountId": "<accountId>"
    },
    "name": "bing_list_ad_creatives"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum image assets to return.
`accountId`	Yes	Account ID listed in BING_ADS_ACCOUNT_IDS. Use the numeric ID, not the eight-character account number shown in the web app.
`maxGroups`	No	Maximum ad groups to scan across those campaigns.
`campaignIds`	No	Optional campaign IDs to scan, up to 20.
`maxCampaigns`	No	Maximum campaigns to scan.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.1Oct 26, 2026

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv1.0.0Oct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

While annotations cover the safety profile (readOnlyHint=true), the description adds valuable functional behavior by stating what the scan *excludes* (delivery, video contents, KPI attribution). This tells the agent precisely what information to expect and what to avoid asking for.

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?

The definition is extremely concise (one sentence) and every clause carries significant weight, detailing the scope of the assets and the limitations of the scan in a highly efficient manner.

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?

Given the comprehensive input schema and the safety annotations, the description is fully complete. It provides the necessary context for a model to confidently select this tool for listing assets while managing user expectations regarding available data depth.

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?

The schema coverage is 100%, so the baseline score of 3 is appropriate. The description mentions 'parent IDs and names,' which clarifies the nature of the returned data but adds little semantic meaning to the inputs beyond what the schema already provides.

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 is highly specific, clearly stating the resource being listed ('image assets') and the context ('account-owned ads and Performance Max asset groups'). This precise focus distinguishes it well from other sibling tools like bing_get_media or bing_get_ads.

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?

The description provides critical usage limitations by specifying a 'Bounded scan.' It explicitly warns that the tool does not return inferred delivery, video content, or KPI attribution, guiding the agent against making false assumptions about the data returned.

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