Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

run_report

Generates custom Microsoft Ads reports with any report type, columns, and date range for campaign, keyword, or account performance analysis.

Instructions

Build-your-own report: any Microsoft Ads report type, any columns, any date range. Use describe_report to look up valid report types and column names.

Common recipes (report_type: useful columns beyond Impressions/Clicks/Spend):

  • Totals for a period: any type with aggregation="Summary" and NO TimePeriod column.

  • Conversions split by goal: CampaignPerformanceReportRequest with Goal, GoalType, Conversions, Revenue (also valid on ad group / keyword / search-term reports).

  • Revenue and return: CampaignPerformanceReportRequest with Revenue, ReturnOnAdSpend.

  • Impression share and why it was lost: CampaignPerformanceReportRequest with ImpressionSharePercent, ImpressionLostToBudgetPercent, ImpressionLostToRankAggPercent.

  • Device split: add DeviceType to a campaign / ad group / keyword report.

  • Whole account: AccountPerformanceReportRequest with AccountName, CurrencyCode.

  • Performance Max asset groups: AssetGroupPerformanceReportRequest.

  • Age and gender: AgeGenderAudienceReportRequest with AgeGroup, Gender. Goal / GoalType cannot share a report with impression-share columns (the API faults RestrictedColumnCombinations, 2064) — run those as two reports. Recipes live-verified 2026-11-17.

aggregation: "Daily" (default) works with any column set; Weekly / Monthly / DayOfWeek / HourOfDay also need the TimePeriod column. "Summary" is only valid when columns exclude TimePeriod — the live API raises InvalidTimePeriodColumnForSummaryReport otherwise.

Dates: days must be 7, 14, or 30. Or pass start_date/end_date (YYYY-MM-DD, both or neither) for an explicit range of any length. Live-verified 2026-08-14 (106-day AccountPerformance custom-range pull).

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": {
      "report_type": "<report_type>",
      "columns": "<columns>"
    },
    "name": "run_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
columnsYes
end_dateNo
start_dateNo
aggregationNoDaily
report_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it names the exact API faults (RestrictedColumnCombinations 2064, InvalidTimePeriodColumnForSummaryReport), the aggregation rules coupling TimePeriod to Weekly/Monthly/DayOfWeek/HourOfDay, and the days-must-be-7/14/30 vs explicit start/end date constraint. That is the kind of failure-mode disclosure an agent needs before calling.

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?

Front-loaded with the one-line purpose, then grouped into recipes, aggregation rules, and date rules with short labeled sections. The recipes list is long but each bullet maps to a distinct use case; the repeated "live-verified" provenance notes are the only wording that does not directly help an agent act.

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?

For a complex, schema-poor tool it covers inputs, constraints, and error modes thoroughly. The remaining gap is on the output side: with no output schema and no annotations, the description never says what a successful call returns (row shape, whether the call blocks or must be polled for a report).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for all six parameters: report_type (examples of valid request types), columns (semantics plus incompatible combinations), aggregation (allowed values and dependent column requirement), days (7/14/30 only), and start_date/end_date (YYYY-MM-DD, both-or-neither, any length).

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?

"Build-your-own report: any Microsoft Ads report type, any columns, any date range" states a specific verb and resource plus scope, and explicitly routes lookup of valid types/columns to the sibling describe_report. An agent can distinguish this arbitrary-report tool from the fixed get_*_performance tools without opening a schema.

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 gives an explicit prerequisite (call describe_report first), concrete selection recipes mapping reporting goals to report_type and column sets, and an exclusion rule (Goal/GoalType cannot be combined with impression-share columns; run as two reports). This is close to a decision tree rather than vague context.

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