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

flin-microsoft-ads-mcp

by flin-agency

get_ads

Read-only

Retrieve responsive search, responsive, expanded text, dynamic search, and product ads for a specified ad group to review available Microsoft Advertising creatives.

Instructions

Get responsive search, responsive, expanded text, dynamic search and product ads.

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

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

C2.7/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 safety is covered; the description adds nothing beyond that. It omits pagination behavior (limit defaults to 100, max 1000) and how account_id/customer_id scoping affects results.

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 front-loaded sentence with no filler and no repetition. It is terse to the point of under-specification rather than wordiness.

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 read-only listing tool with a required parent identifier, no output schema, and undocumented parameters, the description should explain pagination and account scoping. It leaves the agent guessing how to constrain and page results.

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, including the required ad_group_id, so the description carries the full burden and fails to explain any of them. Listing ad types hints at result content but adds no meaning to limit, account_id, or customer_id.

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?

Specific verb ("Get") plus resource ("ads") with the ad subtypes enumerated (responsive search, responsive, expanded text, dynamic search, product). It is distinguishable from siblings like get_ad_groups, get_campaigns, and get_keywords, though it never states the scope (per ad group) or what is returned.

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 mention that ad_group_id is required, and no routing to alternatives for adjacent resources (ad groups, campaigns, keywords). The agent must infer usage entirely from the name and schema.

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