Microsoft Advertising MCP server

Overview Schema Source Related Servers Discussions Admin

bing get videos

bing_get_videos

Read-onlyIdempotent

Read Microsoft Advertising account video assets and their processing status. Use it to confirm which videos are ready for ads, since Active means the media is prepared, not that an ad is delivering.

Instructions

Read account video assets and processing status. Active means the media is ready, not that an ad is delivering.

Input Schema

Name	Required	Description
`page`	No	Zero-based page index.
`pageSize`	No	Videos per page, 1 to 100.
`videoIds`	No	Optional video IDs. Omit to page through every video.
`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.

Changed2 schema fields changedv1.0.1Oct 26, 2026

addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious domain caveat that an 'Active' status refers to media readiness rather than ad delivery, which prevents misinterpretation of results. It does not cover pagination behavior, but that is comparatively minor.

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 with no filler; the core action is stated first and the status caveat follows. Every sentence earns its place.

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?

The schema is fully described, an output schema exists, and annotations cover the safety profile, so the remaining burden on the description is mainly routing and scoping. It leaves the overlap with bing_get_media unresolved, which is the one thing an agent most needs clarified here.

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%, including the important accountId note about numeric IDs versus the web-app account number, and the semantics of videoIds and paging. The description adds nothing beyond what the schema already documents, so 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 account video assets and processing status.' An agent can tell it returns video assets with a processing status. However, it never distinguishes itself from the sibling bing_get_media, which plausibly overlaps in scope.

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 bing_get_media or the other asset-reading siblings, and no prerequisites or exclusions. The 'Active means...' sentence is a semantics caveat, not usage guidance, so the agent is left to infer when to pick this tool.

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