Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Set Final URL Suffix on a Search Channel

set_search_channel_final_url_suffix
Destructive

Set or clear the Final URL Suffix on a wizard campaign's search channel (Google Ads or Microsoft Ads). The suffix is appended to every final URL the platform serves — typically UTM parameters for tracking (utm_source, utm_medium, utm_campaign, ...).

            Matches the platform UI's "Final URL Suffix" input under the Google Ads / Microsoft Ads channel's Advanced Settings section.

            KEYWORDS: final url suffix, final-url-suffix, url suffix, suffix, utm, utm parameters,
            utm source, utm medium, utm campaign, tracking, tracking template, url tracking,
            tracking parameters, google ads, google, microsoft ads, microsoft, bing,
            search channel, search campaign, campaign settings, advanced settings

            WHEN TO USE:
            - Add or change UTM / tracking parameters on Google Ads or Microsoft Ads final URLs
            - Clear an existing suffix (pass empty string "")

            REQUIREMENTS:
            - The campaign MUST already have the target channel enabled (via create_campaign /
              add_and_edit_campaign_elements with a `google` and/or `microsoft` block).
            - Final URL Suffix is search-channel-only. LinkedIn / Meta / Reddit do NOT support
              it and the tool will reject other channel types.

            PARAMETERS:
            - campaign_id (required): the wizard campaign ID.
            - channel (required): "GOOGLE_ADS" or "MICROSOFT_ADS".
            - final_url_suffix (required): the suffix string. Max 2048 chars. Format: key=value
              pairs separated by `&`. Allowed characters: A–Z a–z 0–9 . _ ~ = & { } - or %XX
              percent-encoded. Spaces and [ ] ( ) # ? must be percent-encoded. Pass empty string
              "" to clear.

            EXAMPLES:

            Set UTMs on a Google Ads channel:
            set_search_channel_final_url_suffix({
                "campaign_id": 177214,
                "channel": "GOOGLE_ADS",
                "final_url_suffix": "utm_source=metadata&utm_medium=cpc&utm_campaign={campaignid}"
            })

            Clear the suffix on a Microsoft Ads channel:
            set_search_channel_final_url_suffix({
                "campaign_id": 177214,
                "channel": "MICROSOFT_ADS",
                "final_url_suffix": ""
            })

            RESPONSE: {success, campaign_id, channel_id, channel, applied:{final_url_suffix}, errors?}

            INTEGRATION WITH OTHER TOOLS:
            - Use search_campaigns_by_names / get_campaign_by_wizard_id to find the campaign.
            - Google Ads / Microsoft Ads channels are enabled by create_campaign or
              add_and_edit_campaign_elements with a `google` / `microsoft` block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesWhich search channel on the campaign to update. Final URL Suffix is only supported on these two.
campaign_idYesThe unique identifier of the wizard campaign.
final_url_suffixYesTracking suffix appended to every final URL on this channel. Format: key=value pairs separated by `&`. Allowed characters: A–Z a–z 0–9 . _ ~ = & { } - or %XX percent-encoded. Pass empty string "" to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds meaningful behavioral context: the suffix is appended to every final URL the platform serves, it matches the platform UI's 'Final URL Suffix' input, and it can be cleared by passing an empty string. It also discloses the rejection behavior for unsupported channel types. The only minor gap is that it doesn't explicitly state whether clearing is destructive or reversible, but the annotations already flag destructiveHint=true, so the description adds sufficient context beyond the annotations.

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?

The description is well-structured with clear sections (WHEN TO USE, REQUIREMENTS, PARAMETERS, EXAMPLES, RESPONSE, INTEGRATION WITH OTHER TOOLS). It is longer than average, but every section earns its place: the examples are instructive, the requirements prevent errors, and the integration notes help with workflow. The keyword list is somewhat redundant and could be trimmed, but it doesn't detract significantly from the overall structure.

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?

For a 3-parameter tool with no output schema, the description is remarkably complete. It covers prerequisites (channel must be enabled), constraints (search-channel-only, max 2048 chars, allowed characters), examples for both setting and clearing, the response shape, and integration with sibling tools for finding the campaign. An agent has everything needed to call this tool correctly without opening the schema.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds value by explaining the format of final_url_suffix (key=value pairs separated by `&`, allowed characters, percent-encoding requirements) and by providing two concrete examples showing exact parameter values. It also clarifies the channel enum values and the meaning of passing an empty string. This goes beyond the schema's parameter descriptions.

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 states a specific verb ('Set or clear'), a specific resource ('Final URL Suffix on a wizard campaign's search channel'), and explicitly names the two supported platforms (Google Ads or Microsoft Ads). It also distinguishes itself from sibling tools by noting it is search-channel-only and that LinkedIn/Meta/Reddit do not support it. This is a clear, specific purpose statement that an agent can act on.

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?

The description has an explicit 'WHEN TO USE' section listing two concrete use cases (add/change UTM parameters, clear existing suffix). It also has a 'REQUIREMENTS' section stating the campaign must already have the target channel enabled, and explicitly says the tool will reject other channel types. This is exactly the kind of when-to-use and when-not-to-use guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Metadata MCP Connector toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources