Skip to main content
Glama

set_microsoft_campaign_status

Pause or Resume a live Microsoft Advertising (Bing Ads) 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": {
      "campaignId": "<campaignId>",
      "status": "<status>"
    },
    "name": "set_microsoft_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
accountIdNo
campaignIdYes
customerIdNo
confirmLiveSpendNoRequired when setting status to Active to confirm live ad spending on Microsoft Advertising.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmLiveSpend
      Added value: +{
      +  "description": "Required when setting status to Active to confirm live ad spending on Microsoft Advertising.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

C2.8/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 discloses very little. It implies a state-mutating operation on a live campaign with real spend consequences, but never mentions the confirmLiveSpend requirement, account/customer scoping, permission needs, or whether the change is reversible or immediate.

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

Conciseness5/5

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

A single front-loaded sentence with the action and target stated immediately and no filler. Nothing is wasted, though the brevity is also the source of the gaps elsewhere.

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 5-parameter mutation tool with no annotations, no output schema, and low schema coverage, this description is too thin. An agent cannot learn from it what confirmLiveSpend means operationally, which identifiers are required in practice, or what happens after the status change.

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 only 20%, so the description should compensate, and it adds no parameter meaning at all — accountId, customerId, and campaignId are undocumented in both places. Only confirmLiveSpend and the status enum are explained, and both come from the schema itself.

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 names a specific verb pair (Pause or Resume) and a specific resource (a live Microsoft Advertising / Bing Ads campaign), which is enough for an agent to select it apart from the Google Ads siblings and from publish_campaign_to_microsoft_ads. It does not, however, state that it acts on an existing campaign by ID versus creating one, beyond the word 'live'.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from 'live' that the campaign must already exist and that publish_campaign_to_microsoft_ads is the tool for creating one; nothing in the text routes between them.

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