Microsoft Advertising MCP server

Overview Schema Source Related Servers Discussions Admin

bing get audiences

bing_get_audiences

Read-onlyIdempotent

Retrieve audience configuration for one audience type in a Microsoft Advertising account, optionally filtered by audience IDs, to inspect settings before matching or targeting.

Instructions

Read audience configuration for one audience type. An empty audience does not establish that it can be matched or targeted.

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>",
      "type": "<type>"
    },
    "name": "bing_get_audiences"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Audience type to read.
`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.
`audienceIds`	No	Optional audience IDs. Omit to read every audience of this type.

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds one genuinely useful semantic caveat — that an empty audience does not imply it can be matched or targeted — but says nothing about pagination, rate limits, or what a read returns beyond that.

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?

Two short sentences with the scope stated first and the caveat second. Both carry information; it is tight and front-loaded, just very sparse.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations plus a fully documented schema carry most of the load. Still, for a read tool over six enum branches, the description gives no sense of what configuration fields are returned or how the empty-audience caveat affects downstream decisions.

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%, with enum for type and clear docs for accountId and audienceIds, so the baseline is 3. The phrase 'one audience type' reinforces the enum scoping but adds no format or behavioral detail beyond the schema.

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?

States a specific verb and resource: 'Read audience configuration', scoped to 'one audience type'. It is clearly distinct from sibling getters like bing_get_campaigns or bing_get_targeting, though it does not name a close alternative the way a 5 would.

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?

Usage is only implied by 'Read ... for one audience type' and the schema's note that audienceIds can be omitted. There is no explicit statement of when to use this versus other audience-related calls (e.g. bing_get_targeting) or when not to.

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