Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

update_sitelink_extension

Update an existing sitelink extension by modifying its link text, URL, or descriptions. Partial updates are supported by preserving omitted fields.

Instructions

Update an existing sitelink extension in place (e.g. add or edit its descriptions).

Microsoft replaces the whole sitelink on update, so display text and the final URL are always required; when you omit any field (e.g. to add only descriptions to an existing sitelink) this tool fetches the current extension and re-sends it, so a partial update is safe. Microsoft requires the two description lines together — a sitelink with description1 must also have description2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
final_urlNoNew landing page URL (omit to keep the current one).
description1NoFirst description line, max 35 chars (omit to keep current).
description2NoSecond description line, max 35 chars (omit to keep current).
display_textNoNew link text, max 25 chars (omit to keep the current one).
ad_extension_idYesThe sitelink extension id (from get_ad_extensions).

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?

Description discloses critical behaviors: Microsoft replaces the whole sitelink, the tool fetches current extension for partial updates, and the requirement that description1 and description2 must be provided together. This adds context beyond the readOnlyHint=false annotation.

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?

Description is concise with two paragraphs. First sentence states purpose, second provides behavioral details. No wasted words, front-loaded key information.

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 complexity (mutation, 5 params, output schema exists), the description covers the safe partial update mechanism and important Microsoft constraints. Could mention error handling or prerequisites, but overall complete enough for agent selection.

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?

Input schema has 100% coverage with clear 'omit to keep current' descriptions. The description adds important constraints: display text and final URL are always required (though optional in schema due to fetch) and description pair requirement. This enriches understanding beyond schema.

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 an existing sitelink extension in place', specifying the verb (update), resource (sitelink extension), and scope. It distinguishes from siblings like add_sitelink_extension by implying this is for modifying existing ones.

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 explains the safe partial update behavior due to fetching, but does not explicitly contrast with add_sitelink_extension. It gives context for using this tool vs alternatives, though a clearer when-to-use statement would improve 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