Microsoft Advertising MCP server

Overview Schema Source Related Servers Discussions Admin

bing get conversion goals

bing_get_conversion_goals

Read-onlyIdempotent

Read Microsoft Advertising conversion goal configuration by account and goal type, optionally filtered by goal IDs. Use it to inspect settings; it does not confirm conversions are being recorded.

Instructions

Read conversion goal configuration. This does not establish that conversions are being recorded.

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_conversion_goals"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Conversion goal type to read.
`goalIds`	No	Optional conversion goal IDs. Omit to read every goal of this type.
`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.

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

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-obvious context: that reading goal configuration does not establish that conversions are actually being recorded, which prevents a common misinterpretation. It stops short of mentioning result volume or whether goalIds is capped at 100.

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?

Two short sentences, zero filler, with the core capability front-loaded and the interpretive caveat immediately after. Nothing could be removed without losing signal.

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?

An output schema exists and annotations cover the safety and world-access profile, so the description needn't explain return values or side effects. The only remaining gap is the lack of any note on result volume or pagination when omitting goalIds, which for a read tool capped at 100 IDs would have been worth a clause.

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 the type enum, the goalIds 'omit to read every goal of this type' behavior, and the BING_ADS_ACCOUNT_IDS format all documented in the schema itself. The description adds no parameter information beyond that, so the baseline 3 applies.

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 conversion goal configuration.' An agent can distinguish this from reporting/insight siblings like bing_get_report or bing_get_insights. It does not explicitly name a sibling it should be preferred over, keeping it just short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, and no prerequisites (e.g. that it needs a configured UET tag or that bing_get_uet_tags should be checked first). The second sentence is an interpretation caveat about results, not usage routing, so guidance remains largely absent.

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