Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

add_sitelink_extension

Create a sitelink extension with display text and final URL, optionally attaching it to a campaign or ad group to provide additional links in ads.

Instructions

Create a sitelink 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).
final_urlYesLanding page URL for the sitelink.
description1NoFirst description line shown under the link (max 35 chars). Microsoft requires both description lines together, so pass description1 and description2 as a pair or omit both.
description2NoSecond description line (max 35 chars); see description1.
display_textYesSitelink link text (max 25 chars).
association_typeNo"Campaign" or "AdGroup" (default "Campaign").Campaign

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?

Annotations indicate readOnlyHint: false (write operation), which the description confirms. However, the description adds minimal behavioral context beyond creation and optional attachment. It does not disclose prerequisites (e.g., needing a campaign/ad group), side effects of attachment, or limits on the number of extensions.

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 a single, concise sentence (13 words) that front-loads the essential information. Every word is meaningful, with no redundancy.

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 that an output schema exists (reducing the need to explain return values), the description is fairly complete for a creation tool. It covers the core action and optional attachment. However, it could briefly mention the pairing constraint for descriptions, though the schema already handles that.

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 coverage is 100%, so the baseline is 3. The description does not add any extra meaning beyond what the schema already provides for parameters like entity_id, final_url, etc.

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 the action ('Create'), the resource ('sitelink extension'), and the optional association ('optionally attach to a campaign or ad group'). It effectively distinguishes from sibling tools like update_sitelink_extension (modify) and other extension tools.

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?

The description implies usage for creation, but lacks explicit guidance on when to use this tool versus alternatives (e.g., when to attach vs. create unattached, or comparisons with other extension creation tools). No when-not or exclusion criteria are provided.

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