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

flin-microsoft-ads-mcp

by flin-agency

get_ad_groups

Read-only

Retrieves the ad groups within a specified campaign, with an optional limit and account or customer context, so you can explore campaign structure and review ad group details.

Instructions

Get ad groups for a campaign.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_ad_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
account_idNo
campaign_idYes
customer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of pagination via limit, no indication of what happens when campaign_id is unknown, and no note about which account/customer context is used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is good. But at this length the brevity reflects under-specification rather than economy, since nothing about scoping, paging, or identifiers is conveyed.

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?

With no output schema, no parameter documentation, and only safety annotations, the description carries the burden for a four-parameter tool and does not meet it. An agent cannot tell from this text how results are paged, what the ID parameters mean, or what the response contains.

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, so the schema supplies names and types only. The description implies campaign_id but says nothing about limit (default 100, max 1000), account_id, or customer_id, leaving the two ID parameters — likely the most error-prone — entirely unexplained.

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 gives a specific verb and resource ('Get ad groups') plus a scope ('for a campaign'), which cleanly separates it from get_campaigns and get_ads by resource name. It stops short of explicitly naming a sibling alternative, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. needing a campaign_id obtained from get_campaigns first), and no mention of when a different tool such as get_ads would be the right call. The agent must infer all routing decisions from the name alone.

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