Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

get_effective_url_settings

Read-only

Resolve the effective URL tracking settings (tracking template, final URL suffix, URL custom parameters) for a campaign or ad group, showing which level (ad group, campaign, or account) each is set at.

Instructions

Resolve the effective URL tracking (tracking template, Final URL suffix, URL custom parameters) for a campaign or ad group, and which level set each.

URL tracking follows Microsoft's inherited / override order (keyword > ad > ad group > campaign > account): a value set at a deeper level wins, otherwise it inherits from its parent, ultimately the account-level URL options. So a campaign or ad group can show a null tracking template while the account template is what actually applies. This walks that inheritance chain and returns the effective tracking_url_template / final_url_suffix / url_custom_parameters plus a *_source ("ad_group", "campaign", or "account") for each, so you do not have to manually cross-reference get_account_url_options with the per-entity reads. Also surfaces msclkid_auto_tagging_enabled. Use it to answer "what tracking template actually applies here, and where is it set?" before activating a campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_group_idNoOptional ad group id (within that campaign) to resolve at the ad-group level; omit to resolve at the campaign level.
campaign_idYesThe campaign id to resolve settings for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelYes
ad_group_idNo
campaign_idYes
final_url_suffix_sourceNo
effective_final_url_suffixNo
msclkid_auto_tagging_enabledNo
tracking_url_template_sourceNo
url_custom_parameters_sourceNo
effective_tracking_url_templateNo
effective_url_custom_parametersNo
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds significant behavioral detail: walks inheritance chain (keyword > ad > ad group > campaign > account), returns null for inherited values, includes source fields and msclkid_auto_tagging_enabled. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is efficiently structured, front-loaded with purpose and inheritance explanation. Slightly long but every sentence adds value. Could be more concise but not overly verbose.

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?

Given annotations, schema, and output schema, the description fully covers tool behavior: inheritance logic, source tracking, and additional field. No missing context for an agent to correctly invoke and interpret results.

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% with detailed descriptions for both parameters. Description does not add further parameter-level meaning beyond what schema already provides, meeting the baseline.

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 the tool resolves effective URL tracking settings (tracking template, suffix, custom parameters) and identifies which level set each. It explicitly distinguishes from sibling tools like get_account_url_options by explaining it returns effective values with source, avoiding manual cross-referencing.

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?

Explicitly states use case: 'answer what tracking template actually applies here, and where is it set?' before activating a campaign. Also explains it avoids manual cross-referencing across per-entity reads. Does not explicitly state when not to use, but context is clear.

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