Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

update_conversion_goal

Update a Microsoft Advertising conversion goal by specifying only the fields to change. Control bidding inclusion, status, revenue model, and lookback window.

Instructions

Update a conversion goal in place. Only the fields you pass change.

The key bidding lever is exclude_from_bidding — the inverse of the web UI's "Include in conversions" checkbox. exclude_from_bidding=false keeps the goal in the Conversions column and in automated-bidding math (ECPC / tCPA); true drops it from both (it still reports under All conversions). Confirm this is false before relying on a goal to steer spend. Read the current values first with get_conversion_goals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew goal name (rename).
statusNo"Active" or "Paused" (a paused goal stops recording conversions).
goal_idYesThe conversion goal id (from get_conversion_goals).
count_typeNoHow conversions are counted per click — "All" (every conversion) or "Unique" (one per click).
revenue_typeNoConversion value model — "FixedValue" (same value each time, requires revenue_value), "VariableValue" (value sent with the event), or "NoValue". Revenue fields are merged onto the goal's current revenue, so you can change one without re-stating the others.
revenue_valueNoRevenue amount (required for "FixedValue"; the default for "VariableValue").
exclude_from_biddingNofalse = include the goal in the Conversions column and automated bidding; true = exclude it from both (still tracked under All conversions).
revenue_currency_codeNoISO currency code for the revenue value, e.g. "USD".
conversion_window_in_minutesNoClick-to-conversion lookback window in minutes (e.g. 43200 = 30 days).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
idsNo
messageYes
partial_errorsNo
Behavior5/5

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

Beyond the annotation indicating a write operation, the description details the selective update behavior ('Only the fields you pass change'), explains the critical exclude_from_bidding parameter's effect on bidding and reporting, and notes that revenue fields are merged. This adds significant value beyond annotations.

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?

The description is concise with no extraneous information. It front-loads the core purpose, then provides focused details on the most important parameter. Every sentence contributes value.

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

Completeness4/5

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

Given the tool has 9 parameters and an output schema (not shown but noted), the description covers essential behavioral aspects and usage context. It could be slightly more complete by mentioning the output format, but the output schema likely handles that.

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

Parameters4/5

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

All 9 parameters have schema descriptions (100% coverage), so baseline is 3. The description adds extra meaning by highlighting exclude_from_bidding as the 'key bidding lever' and clarifying the merge behavior for revenue fields, raising the score to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Update a conversion goal in place' which specifies the verb (update) and resource (conversion goal). It distinguishes itself from create_conversion_goal and get_conversion_goals, as noted in sibling tools.

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

Usage Guidelines4/5

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

The description advises to 'Read the current values first with get_conversion_goals' before updating, providing clear context on when to use this tool. It also warns about the exclude_from_bidding parameter being the inverse of the UI checkbox, though it doesn't explicitly state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinypebble/microsoft-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server