Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

add_call_extension

Create a call extension for Microsoft Ads and attach it to a campaign or ad group to add a clickable phone number in ads.

Instructions

Create a call extension and optionally attach it to a campaign or ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idNoCampaign or ad group id to associate it with (omit to create unattached).
country_codeNoTwo-letter country code for the number (default "US").US
is_call_onlyNoWhether the extension shows only the phone number (no website click).
phone_numberYesThe phone number to show (e.g. "2065550100").
association_typeNo"Campaign" or "AdGroup" (default "Campaign").Campaign
is_call_tracking_enabledNoTurn on Microsoft call tracking (US/UK only) so call-from-ad conversions are measured. Microsoft displays a forwarding number instead of the raw number; new forwarding numbers are local (toll-free is no longer provisioned).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
idsNo
messageYes
partial_errorsNo
Behavior2/5

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

The description merely states 'Create' which aligns with annotations (readOnlyHint: false), but adds no further behavioral context (e.g., permissions, limits, side effects). Key behavioral details are relegated to parameter descriptions.

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?

Single sentence, no wasted words. Front-loaded with the core action.

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?

For a creation tool with an output schema (not shown), the description adequately covers the core action and optional attachment. It implicitly covers context given the sibling list and parameter count.

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?

Since schema description coverage is 100%, the baseline is 3. The description adds no extra meaning beyond the schema's already detailed parameter documentation.

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?

Description clearly states 'Create a call extension' with a specific verb and resource, and distinguishes from sibling tools like 'update_call_extension' and 'add_callout_extension'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives such as 'update_call_extension'. The description implies usage for creation but lacks exclusions or context.

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