Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

get_ad_performance

Retrieves daily ad metrics—impressions, clicks, spend, conversions, and click-through rate—for a chosen 7, 14, or 30-day window, organized by campaign and ad group.

Instructions

How each ad did, day by day: impressions, clicks, spend, conversions, click-through rate, with its campaign and ad group.

days must be 7, 14, or 30 (one row per day). For any other date range, other columns, or totals instead of daily rows, use run_report.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ad_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/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 well: it discloses the fixed 7/14/30 window constraint, the row grain, and the returned fields. It stops short of stating read-only/auth requirements or any row-limit behavior, but the behavioral shape of the response is clear.

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 sentences, front-loaded with what is returned and followed by the constraint plus the escape hatch to run_report. No wasted wording.

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?

There is no output schema, so the description must describe return values, which it does at field level including the joined campaign and ad group. A single optional parameter keeps requirements low; only auth/permission expectations and result-size behavior are absent.

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

Parameters4/5

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

Schema coverage is 0% and the schema only shows an integer 'days' with default 30, so the description is the sole source of meaning. It supplies the crucial enum constraint (7, 14, or 30), which the bare schema omits entirely; only the default is left to the schema.

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?

The description names the resource (ad-level performance), the grain (day by day, one row per day), and the exact metrics returned (impressions, clicks, spend, conversions, CTR, campaign, ad group). That is enough for an agent to distinguish it from run_report and from the campaign/keyword/geo performance siblings.

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 states the allowed values ('days must be 7, 14, or 30') and explicitly routes out-of-scope requests to run_report for other date ranges, other columns, or totals instead of daily rows. Both the when and the when-not/alternative are spelled out.

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