Skip to main content
Glama
Sign In
Microsoft Advertising MCP server

Microsoft Advertising MCP server

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bing get report

bing_get_report
Read-onlyIdempotent

Retrieve generated CSV reports for your Bing Ads account. Provide the account ID and receipt to download report data, up to 2,000 rows.

Instructions

Poll and download a report submitted by bing_get_insights for the same account. Returns up to 2,000 CSV rows as strings; narrow the range when truncated is true. Empty sandbox output is not production evidence.

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>",
      "receipt": "<receipt>"
    },
    "name": "bing_get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesReceipt returned by bing_get_insights in this server session. It expires after one hour.
accountIdYesAccount ID listed in BING_ADS_ACCOUNT_IDS. Use the numeric ID, not the eight-character account number shown in the web app.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed1 schema field changedv1.0.1
    • 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"
+  }
+]
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so safety is covered; the description adds real substance beyond them — the 2,000-row cap, that rows come back as strings, the truncation signal and how to respond to it, and a warning that empty sandbox output is not production evidence. It does not spell out what 'poll' means on a not-yet-ready report (retry vs error).

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?

Three short sentences, each carrying distinct information: workflow dependency, result shape/limits, and a data-integrity caveat. The final caveat is slightly cryptic out of context (what 'sandbox' refers to is assumed), but nothing is padded.

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, so return values need not be re-explained; the description nonetheless covers the row limit and truncation behavior, plus the required upstream call. Complete for correct invocation, with only the poll-not-ready semantics left implicit.

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%, and the schema itself documents the receipt's one-hour expiry and the accountId format constraint (numeric ID, not the eight-character number). The description adds only the linkage that the receipt comes from bing_get_insights, so baseline 3 applies.

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?

States a specific verb pair (poll and download) and resource (report), and explicitly ties it to the sibling bing_get_insights that produced the receipt. An agent can distinguish it from the other bing_get_* tools, which fetch data directly rather than poll a queued report.

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

Usage Guidelines4/5

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

Clear context: use this only after bing_get_insights has submitted a report for the same account, since it requires that tool's receipt. It also gives an in-call remedy (narrow the range when truncated is true). No explicit exclusions or alternative tools are named, but the workflow gate is unambiguous.

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

Deploy Server

Other Tools