Microsoft Advertising MCP server

Overview Schema Source Related Servers Discussions Admin

bing get campaigns

bing_get_campaigns

Read-onlyIdempotent

Read campaign configuration, budgets, settings, and status for a specified campaign type; repeat per type to inventory all campaigns in an account.

Instructions

Read native campaign configuration, budget, settings and status for one campaign type. Repeat for other types to inventory the whole account.

Input Schema

Name	Required	Description	Default
`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.
`campaignType`	Yes	Campaign type to read. Call once per type for a full inventory.

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.5/5.0

Behavior4/5

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

The annotations provide strong safety guarantees (readOnlyHint: true, destructiveHint: false). The description complements this by defining the scope of information retrieved (configuration, budget, settings) without repeating the explicit safety metadata.

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 two sentences are highly efficient and front-loaded. Every part of the description contributes directly to clarifying the tool's function or logic.

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 large list of sibling tools, it clearly specifies that this function operates on 'Campaign' resources, preventing the agent from mistakenly invoking it for ad groups, keywords, or assets.

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 coverage is 100%. While the description provides useful high-level context on the necessity of multiple calls, it adds no semantic meaning to the individual parameters beyond what the schema already specifies.

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 explicitly states the function—reading native campaign configuration, budget, settings, and status—immediately distinguishing it from other `bing_get_` tools which might handle Ads, Keywords, or Targeting.

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?

It provides clear instructions on usage by stating, 'Repeat for other types to inventory the whole account,' which dictates the agent's operational flow for account-wide tasks.

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