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

flin-microsoft-ads-mcp

by flin-agency

get_campaigns

Read-only

Retrieve campaigns across supported campaign types, using configured IDs when account or customer IDs are omitted.

Instructions

Get campaigns across supported campaign types; IDs can default from configuration.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
account_idNo
customer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 genuinely useful behavior—identifiers can be omitted and resolved from configuration, meaning an empty call is valid—but says nothing about pagination, result volume, or what campaign types come back despite openWorldHint implying external variability.

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 with the operation front-loaded and no filler. The semicolon clause is slightly compressed to the point of ambiguity about which IDs are meant, but nothing is wasted.

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?

Three parameters with zero schema description coverage, no output schema, and an open-world scope—yet the description covers only the ID-defaulting behavior and leaves limit semantics, result shape, and campaign-type breadth unexplained. It is under-specified relative to the tool's surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden; it explains the otherwise opaque defaulting behavior for account_id and customer_id ('IDs can default from configuration'), which is real added meaning. However, the limit parameter and its 1–1000 range/100 default are never mentioned, and it is unclear whether 'IDs' covers both ID fields or only one.

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?

States a specific verb and resource ('Get campaigns') and adds scope ('across supported campaign types'), which distinguishes it from the other list-style siblings like get_ads and get_ad_groups. It stops short of naming which campaign types are supported or how it differs from get_insights, but the core operation is unambiguous.

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, and no reference to alternatives; the agent must infer from the name alone that this is the campaigns lister. The 'IDs can default' clause hints at a zero-argument call path but is not framed as usage guidance.

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