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 account-owned ads and Performance Max asset groups, returning parent IDs and names for inventory checks and asset mapping.

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.

Input Schema

TableJSON 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

TableJSON 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.

First observedv1.0.0Oct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond annotations: it is a bounded scan and explicitly does not infer delivery, video contents, or KPI attribution. Auth and pagination behavior are not described, so it stops short of 5.

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 definition is two sentences and front-loaded with the core purpose. The second sentence is compact and informative, though 'Bounded scan' is slightly opaque without referencing the limit controls directly.

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?

With an output schema present, all parameters documented at 100% coverage, and annotations covering safety, the description supplies enough scope and non-goal context for correct invocation. It does not add return-shape detail, but the output schema already covers that.

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 100%, so the schema already documents all five parameters. The description alludes to bounded scanning and parent IDs/names, but adds no parameter syntax or meaning beyond what the schema provides; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('List'), resource ('image assets'), and scope ('account-owned ads and Performance Max asset groups'), plus output detail ('parent IDs and names'). It indirectly distinguishes itself from video-oriented siblings by excluding video contents, but it does not explicitly name a sibling alternative.

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 exclusions ('no inferred delivery, video contents or KPI attribution') imply when this tool is and is not appropriate, but there is no explicit when-to-use guidance and no named alternative such as bing_get_media or bing_get_videos. Usage must be inferred from scope.

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