Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

describe_report

Look up valid report types and their column names before calling run_report, avoiding guessed inputs without making an API call.

Instructions

Look up what run_report accepts — call this before run_report instead of guessing names. No argument: every report type. With a report_type (e.g. 'CampaignPerformanceReportRequest'): every valid column name for it. Read offline from Microsoft's own API definition shipped with the SDK; makes no API call.

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": "describe_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.8/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 that the data is read offline from Microsoft's shipped API definition and that no API call is made, which tells the agent this is a cheap, side-effect-free lookup. It stops short of describing the literal response shape (e.g. a list of strings vs. objects), which is the only remaining behavioural gap.

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?

Three tight sentences, front-loaded with the action and the routing directive; the no-argument vs. with-argument split is presented as a clean contrast. No filler or restated metadata.

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

Completeness5/5

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

For a single optional parameter, no annotations and no output schema, the description covers everything an agent needs: what it returns in each mode, where the data comes from, and that it triggers no network activity. Nothing essential is missing.

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% and the schema only says 'Report Type', so the description must compensate — and it does, giving a concrete example value ('CampaignPerformanceReportRequest') and defining the semantics of both the null and populated cases. That is meaningful meaning well beyond 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?

States a specific verb and resource ('look up what run_report accepts') and immediately positions itself relative to the sibling run_report, so an agent can tell the two apart without opening either schema. The two-mode behaviour (all report types vs. columns for one type) is spelled out in the same breath.

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 directive — call this before run_report instead of guessing names — naming both the alternative tool and the failure mode it prevents. The when-to-use distinction between omitting and supplying report_type is also explicit.

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