Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

update_call_extension

Update a call extension's phone number, country, or call tracking settings. Preserves existing data when toggling single fields.

Instructions

Update an existing call extension in place (e.g. the brand's phone number or tracking).

Microsoft replaces the whole call extension on update, so phone number and country code are always required; when you omit them (e.g. to flip only is_call_tracking_enabled) this tool fetches the current extension and re-sends them, so a single-field toggle is safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeNoTwo-letter country code for the number, e.g. "US" (omit to keep current).
is_call_onlyNoWhether the extension shows only the phone number (no website click).
phone_numberNoNew phone number (omit to keep the current one).
ad_extension_idYesThe call extension id (from get_ad_extensions).
is_call_tracking_enabledNoTurn Microsoft call tracking on/off (US/UK only). When on, Microsoft displays a forwarding number so call conversions are measured (new forwarding numbers are local, not toll-free). Pass true to enable tracking on an existing plain call asset.

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 readOnlyHint=false annotation, the description details the replacement behavior and the fetch mechanism for omitted fields, giving full transparency on the tool's actions.

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?

Two sentences that cover purpose, behavioral implications, and safe usage with no redundant information.

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

Completeness5/5

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

With 100% schema coverage, annotations, and an output schema, the description completes the picture by focusing on the key nuance (whole replacement) that is not obvious from structured data.

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

Parameters5/5

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

Adds critical context beyond the schema, clarifying that country_code and phone_number are required in the API even though the schema allows null defaults, and explains the behavior when omitted.

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?

Clearly states 'Update an existing call extension' with specific examples (brand's phone number or tracking), differentiating from sibling tools like add_call_extension and delete_ad_extension.

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

Usage Guidelines5/5

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

Explicitly explains that Microsoft replaces the whole extension and that phone number and country code are always required, while also providing the safe toggle behavior for partial updates via fetching current values.

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