Skip to main content
Glama

list_microsoft_ads_campaigns

List Microsoft Advertising (Bing Ads) campaigns under the user's connected AccountId.

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": "list_microsoft_ads_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNoMicrosoft Ads AccountId (optional if set in your MCP token).
customerIdNoMicrosoft Ads CustomerId (optional if set in your MCP token).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only weakly signals read-only via the verb 'List'. It says nothing about pagination, result caps, whether paused/removed campaigns are included, rate limits, or what happens when no account is connected.

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 the platform qualifier placed before the resource, so an agent parses the intent immediately. Nothing is padded, though the brevity leaves no room for the usage context noted above.

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

Completeness3/5

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

This is a simple two-parameter read operation with full schema documentation and no output schema to explain, so the low detail is largely defensible. The remaining gap is behavioral: an agent cannot tell from the description what the listing returns or how it behaves for an account with many campaigns.

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 description coverage is 100%, so both accountId and customerId are already documented, including the 'optional if set in your MCP token' fallback behavior. The description only echoes the AccountId scoping and never mentions customerId, adding no meaning beyond the schema.

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 states a specific verb and resource ('List ... campaigns') plus the platform disambiguation ('Microsoft Advertising (Bing Ads)'), which cleanly separates it from the Google Ads siblings in the catalog. It stops short of naming a contrasting sibling (e.g. publish_campaign_to_microsoft_ads) as a positive routing cue, so it is clear but not maximally differentiating.

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?

The only usage-relevant content is the scope phrase 'under the user's connected AccountId', which implies a read of the already-connected account. There is no statement of when to prefer this over publish_campaign_to_microsoft_ads or set_microsoft_campaign_status, and no exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources