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

flin-microsoft-ads-mcp

by flin-agency

get_keywords

Read-only

Retrieve configured keywords for a specified ad group, with optional account/customer filters and a result limit, to inspect keyword setup; use search term insights for actual search queries.

Instructions

Get configured keywords; use search_term insights for actual search queries.

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": {
      "ad_group_id": "<ad_group_id>"
    },
    "name": "get_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
account_idNo
ad_group_idYes
customer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful distinction between configured keywords and observed queries, but says nothing about result volume, pagination behavior, or whether results are scoped across accounts.

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?

A single compact sentence that front-loads the tool's action and follows with the routing hint; no filler. It is perhaps too terse for a four-parameter tool, but there is no wasted wording to cut.

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

Completeness2/5

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

For a list tool with four undocumented parameters, no output schema, and defaulted scope fields, the description should clarify what is returned and how account/customer/ad group identifiers interact. None of that is present, so an agent can call it but cannot confidently predict the result set.

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% across four parameters (limit, account_id, customer_id, ad_group_id), so the schema supplies names only. The description does not explain the meaning of the ad_group_id requirement, what account_id/customer_id scoping does when defaulted to empty, or the limit's default of 100 and cap of 1000, leaving the agent to guess.

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?

"Get configured keywords" gives a specific verb and resource, and the qualifier "configured" signals these are stored keyword settings rather than query data. It also names a contrasting resource (search_term insights), which helps an agent separate the two, though it does not differentiate against any of the listed siblings like get_ad_groups or get_ads.

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

Usage Guidelines4/5

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

The second clause routes the agent away from this tool when the goal is actual search queries, pointing to search_term insights instead. That is a genuine when-not/alternative instruction, but it covers only one alternative and gives no guidance on prerequisites such as which account/customer/ad group scope to supply.

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