Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

get_geo_performance

Retrieves daily geographic performance for your Microsoft Ads campaigns—country, state, metro, and city—with impressions, clicks, spend, and conversions over the last 7, 14, or 30 days.

Instructions

Where the clicks came from, day by day: country, state, metro area, city, with impressions, clicks, spend, conversions.

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_geo_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 reveals the return granularity (one row per day), the exact columns/metrics, and the constrained input values. It does not state permission requirements, error behavior for invalid `days`, or account/scope assumptions, leaving some behavioral gaps.

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 blocks, zero filler: first what the tool returns, then the constraint and the routing to the alternative. The most decision-relevant information is front-loaded.

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 simple one-parameter read tool with no output schema and no annotations, the description covers output content, granularity, and input constraints adequately. Minor gaps remain around invalid-input behavior and account scope, but nothing essential for a correct call is missing.

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% for the single `days` parameter, so the description must compensate, and it does: it specifies the enum-like constraint (7, 14, or 30) and explains that it controls one-row-per-day output. It doesn't clarify the default (30 in schema) or what happens with other values beyond the redirect to run_report.

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 exact resource and breakdown (geo: country, state, metro, city) plus the metrics returned (impressions, clicks, spend, conversions), so an agent knows precisely what this tool produces. It also implicitly distinguishes itself from the broad reporting tool by describing a fixed, narrow shape.

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 when-not and a named alternative: 'For any other date range, other columns, or totals instead of daily rows, use run_report.' It also states the allowed `days` values, which is a hard precondition for a correct call.

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