Skip to main content
Glama
flin-microsoft-ads-mcp

flin-microsoft-ads-mcp

by flin-agency

get_insights

Read-only

Retrieve Microsoft Advertising performance insights for a date range, including clicks, impressions, spend, conversions, and revenue by account, campaign, ad group, ad, keyword, or search term.

Instructions

Performance report for inclusive YYYY-MM-DD dates (up to 367 days). Includes clicks, impressions, spend, conversions and revenue. Can take up to two minutes; recent data may be incomplete. Search terms may be limited by Microsoft's privacy rules.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyNo
levelNocampaign
limitNo
end_dateYes
timezoneNoAmsterdamBerlinBernRomeStockholmVienna
account_idNo
start_dateYes
customer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), and the description adds real behavioral context beyond them: a latency warning ('can take up to two minutes'), a data-freshness caveat ('recent data may be incomplete'), and a privacy-driven truncation of search terms. These are non-obvious traits an agent needs to plan timeouts and interpret results. It does not mention pagination or how limit interacts with totals.

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?

Four tight sentences, front-loaded with purpose and the date constraint, then latency and caveats. Every sentence adds information; nothing is redundant. It could be marginally better organized with the caveats grouped, but it is efficiently written.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description partially compensates by listing the metric fields returned. However, for an 8-parameter analytics tool with 0% schema description coverage, it leaves the level/timezone/limit/account_id/customer_id semantics and result shape (rows per day per level?) unclear, which are exactly the choices an agent must get right before calling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it only documents the date parameters (inclusive YYYY-MM-DD format, max 367 days). The six remaining parameters — level, daily, limit, timezone, account_id, customer_id — get no explanation at all in either structured or unstructured form, including whether level changes granularity and how daily aggregates the output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Performance report' for a date range) and enumerates the metrics returned (clicks, impressions, spend, conversions, revenue), so an agent can tell this is the analytics tool rather than an entity-listing sibling like get_campaigns or get_keywords. It stops short of explicitly naming those siblings as alternatives, but the purpose itself is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the metrics and date-range framing: use this for aggregated performance over a period. There is no explicit statement of when to prefer this over the sibling entity tools, and no guidance on level selection trade-offs (e.g. account vs keyword) beyond the schema enum. Useful implicit context, but no true when/when-not routing.

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