Skip to main content
Glama
mcp-microsoft-ads

mcp-microsoft-ads

by wvuhskr

get_search_terms

Retrieve daily search terms with matched keywords, impressions, clicks, spend, and conversions to identify wasted spend and negative-keyword candidates; use for 7-, 14-, or 30-day windows.

Instructions

What people actually typed before clicking (search terms report), day by day, with the keyword that matched and impressions, clicks, spend, conversions. The usual starting point for finding wasted spend and negative-keyword candidates.

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_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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 the returned fields (keyword matched, impressions, clicks, spend, conversions), the daily row granularity, and the allowed day values. It doesn't mention pagination, limits, or auth, but for a read-only report tool the main behavioral traits are covered.

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?

The description is front-loaded with what the report contains and its primary use case, followed by the parameter constraint and alternative. Every sentence earns its place, with no redundant wording. It is appropriately sized for a one-parameter report tool.

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?

Given one optional parameter, no annotations, and no output schema, the description provides everything needed: purpose, daily row granularity, returned columns, allowed day values, and the alternative for other report shapes. Nothing essential for correct invocation 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%, so the description must compensate, and it does: it constrains days to 7, 14, or 30 and explains that each day produces one row. It also routes other date ranges to run_report, which the schema does not capture because days has no enum. This adds essential meaning beyond the input 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 states a specific resource and verb: the search terms report, showing what users typed before clicking. It clearly distinguishes this from the sibling run_report by emphasizing daily rows and fixed day windows. An agent can identify the tool's purpose without opening the schema or other tools.

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 explicitly positions the tool as the starting point for finding wasted spend and negative-keyword candidates. It also states exactly when to use run_report instead: for any date range other than 7/14/30, other columns, or totals instead of daily rows. This covers both when to use and the alternative.

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