Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

get_keyword_performance

Retrieve daily keyword performance for the last 7, 14, or 30 days, including match type, impressions, clicks, spend, conversions, cost per conversion, and Quality Score.

Instructions

How each keyword did, day by day: match type, impressions, clicks, spend, conversions, cost per conversion, Quality Score.

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_keyword_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 disclosure burden and does well: it states output granularity (one row per day), the metric set, and the fixed window values. It stops short of mentioning pagination, row limits, or whether all keywords in the account are covered, which are relevant for a reporting call.

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, zero filler: the metric list is front-loaded and the constraint plus sibling routing follows. Every clause earns its place.

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?

No output schema or annotations exist, so the description must define the result shape, and it does by naming columns and daily row granularity. It is nearly complete, but leaves open keyword scoping (account-wide vs. filtered) and result-size behavior.

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 single parameter has no enum, so the description's 'days must be 7, 14, or 30' is the only place the allowed values appear — a real value-add over the bare integer with default 30. It still does not clarify whether the window is a lookback from today or a timezone basis.

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 and resource ('how each keyword did, day by day') and enumerates the returned columns, which makes keyword-level granularity unmistakable against the ad/campaign performance siblings. An agent can tell what it retrieves without opening the 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?

Gives an explicit routing rule: 'For any other date range, other columns, or totals instead of daily rows, use run_report.' It names the alternative and the exact conditions that select it, plus the constraint that days must be 7, 14, or 30.

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