Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Update LinkedIn Channel Settings

update_linkedin_channel_settings
Destructive

Update the LinkedIn channel settings of an existing DRAFT wizard campaign: native objective, bidding optimization goal (including Reach), bid strategy with manual bid amount, and the LinkedIn conversion actions the campaign optimizes toward.

            These are the settings the platform UI shows in the LinkedIn channel drawer of the
            campaign draft page (Native Objective, Bidding Optimization Goal, Bid, Conversion
            Actions). The campaign MUST already have its LinkedIn channel enabled (via
            create_campaign / add_and_edit_campaign_elements with a `linkedin` block).

            WARNING: DRAFT-ONLY: the platform rejects these edits once the campaign is Launching/Launched.

            KEYWORDS: linkedin, linkedin campaign, linkedin settings, campaign settings, draft campaign,
            objective, native objective, brand awareness, website visits, engagement, video views,
            bidding optimization goal, optimization goal, reach, impressions, landing page clicks,
            engagement clicks, bid, bid strategy, auto bid, manual bid, maximum delivery,
            conversion, conversions, conversion actions, conversion tracking, insight tag, settings

            WHEN TO USE:
            - Set the LinkedIn native objective (e.g. Brand Awareness instead of the default Engagement)
            - Optimize a Brand Awareness campaign for REACH instead of IMPRESSIONS
            - Switch between auto bid (LinkedIn maximum delivery) and a manual bid
            - Pick which LinkedIn conversion actions the campaign optimizes toward and reports on

            PARAMETERS (campaign_id required; everything else optional, and an unspecified
            setting keeps its current value on the channel):
            - campaign_id: the wizard campaign ID
            - objective: BRAND_AWARENESS | WEBSITE_VISIT | ENGAGEMENT | VIDEO_VIEW, the LinkedIn
              native objective. Only selectable on Brand Awareness (CTR) campaigns: a Lead Gen
              (CPL) campaign derives it from its offer at launch (lead-gen form -> LEAD_GENERATION,
              landing page -> WEBSITE_CONVERSION). The platform default for a new LinkedIn channel
              is ENGAGEMENT. Every ad already on the channel must be supported by the objective
              (VIDEO_VIEW is video-only, MESSAGE ads only fit WEBSITE_VISIT, DOCUMENT ads lock the
              objective, a video-only channel accepts only ENGAGEMENT or VIDEO_VIEW). A channel
              holding CTV ads is always Brand Awareness / Reach at launch and cannot be changed here.
              Changing the objective also resets the cost type and the bidding optimization goal to
              the objective's default (BRAND_AWARENESS -> IMPRESSIONS, WEBSITE_VISIT ->
              LANDING_PAGE_CLICKS, ENGAGEMENT -> ENGAGEMENT_CLICKS, VIDEO_VIEW -> VIDEO_VIEWS), so
              pass bidding_optimization_goal in the same call when you want something else.
            - bidding_optimization_goal: what LinkedIn optimizes delivery for. Allowed per objective:
              BRAND_AWARENESS -> IMPRESSIONS | REACH; WEBSITE_VISIT -> LANDING_PAGE_CLICKS |
              IMPRESSIONS; ENGAGEMENT -> ENGAGEMENT_CLICKS | IMPRESSIONS; VIDEO_VIEW -> VIDEO_VIEWS |
              IMPRESSIONS. Conversation and Message ads are always IMPRESSIONS. CTR campaigns only.
            - bid_strategy: AUTO_BID (LinkedIn "maximum delivery", what the campaign builder applies
              by default) or MANUAL_BID (needs bid_amount). CTV ads REQUIRE AUTO_BID; Spotlight and
              Text ads REQUIRE MANUAL_BID.
            - bid_amount: manual bid in the account currency, used only with MANUAL_BID.
            - conversion_action_ids: ids of LinkedIn conversion actions (from list_linkedin_conversions)
              the campaign should optimize toward and count as conversions: website visits, URL-rule
              page views, lead form fills. REPLACES the current selection; pass [] to clear it (the
              campaign then falls back to the account's default Insight Tag URL match). Every id must
              exist and be enabled on the connected LinkedIn account, or launch validation fails.
              NOTE: the platform UI only shows this picker for campaigns with landing-page offers and
              an objective other than Brand Awareness; ids stored outside that case are still sent to
              LinkedIn at launch, but that path is not exercised by the UI.

            NOT SETTABLE ANYWHERE IN THE PLATFORM (say so instead of promising them): LinkedIn
            Audience Network on/off and its category exclusions, audience expansion (campaigns always
            launch with expansion OFF), frequency caps, Thought Leader ads. LinkedIn geo targeting is
            not a channel setting either: it lives on the audience / target group.

            EXAMPLES:

            Brand Awareness optimized for Reach on auto bid:
            update_linkedin_channel_settings({"campaign_id": 12345, "objective": "BRAND_AWARENESS",
                "bidding_optimization_goal": "REACH", "bid_strategy": "AUTO_BID"})

            Track two conversion actions on a Website Visits campaign:
            update_linkedin_channel_settings({"campaign_id": 12345,
                "conversion_action_ids": ["123456", "234567"]})

            RESPONSE: {success, campaign_id, channel_id, campaign_status, campaign_goal,
            channel_ad_types, applied:{...}, errors?}. `applied` echoes exactly what was pushed to
            the platform.

            INTEGRATION WITH OTHER TOOLS:
            - list_linkedin_conversions lists the conversion actions available on the account
            - search_campaigns_by_names / get_campaign_by_wizard_id to find the campaign
            - The LinkedIn channel is enabled by create_campaign or add_and_edit_campaign_elements
            - check_campaign_launch_readiness validates the result before launch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectiveNoLinkedIn native objective. Brand Awareness (CTR) campaigns only; Lead Gen campaigns derive it from the offer at launch. Resets the bidding optimization goal to the objective's default.
bid_amountNoManual bid amount in the account currency. Applied only with MANUAL_BID.
campaign_idYesThe unique identifier of the wizard campaign
bid_strategyNoAUTO_BID = LinkedIn maximum delivery (required for CTV ads); MANUAL_BID needs bid_amount (required for Spotlight and Text ads).
conversion_action_idsNoLinkedIn conversion action ids from list_linkedin_conversions. REPLACES the channel's selection; [] clears it.
bidding_optimization_goalNoWhat LinkedIn optimizes delivery for. Must fit the channel's objective: BRAND_AWARENESS takes IMPRESSIONS or REACH, WEBSITE_VISIT takes LANDING_PAGE_CLICKS or IMPRESSIONS, ENGAGEMENT takes ENGAGEMENT_CLICKS or IMPRESSIONS, VIDEO_VIEW takes VIDEO_VIEWS or IMPRESSIONS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond that: it warns the platform rejects edits once the campaign is Launching/Launched, explains that changing the objective resets cost type and bidding optimization goal, states that conversion_action_ids REPLACES the current selection and [] clears it, and discloses that some settings are not settable anywhere in the platform. It also notes the UI-only picker caveat for conversion actions. This is rich behavioral disclosure with no contradiction.

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 long but every section earns its place: purpose, DRAFT-ONLY warning, keywords, when-to-use, parameter semantics, not-settable list, examples, response shape, and integration with other tools. It is front-loaded with the core purpose and the critical DRAFT-ONLY constraint. The only minor deduction is that the keyword list and the extensive parameter prose could be trimmed without losing value, but the structure is clear and scannable.

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 complex mutation tool with 6 parameters, no output schema, and destructive annotations, the description is remarkably complete: it covers prerequisites (channel must be enabled), constraints (draft-only, ad-type requirements), side effects (objective resets), response shape, and integration with sibling tools. The examples demonstrate realistic calls. Nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds substantial meaning beyond the schema: per-objective allowed bidding goals, the fact that CTV ads REQUIRE AUTO_BID while Spotlight/Text ads REQUIRE MANUAL_BID, the default ENGAGEMENT objective, the lead-gen derivation rule, and the fallback to the account's default Insight Tag URL match when conversion_action_ids is cleared. It also explains the reset behavior when objective changes. This far exceeds the schema's 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 opens with a specific verb and resource: 'Update the LinkedIn channel settings of an existing DRAFT wizard campaign' and enumerates exactly which settings are affected (native objective, bidding optimization goal, bid strategy, conversion actions). It also distinguishes itself from siblings by scoping to the LinkedIn channel drawer of the campaign draft page and by naming related tools like create_campaign, add_and_edit_campaign_elements, and list_linkedin_conversions. The DRAFT-ONLY warning further disambiguates it from launch-time tools.

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 four concrete scenarios (set native objective, optimize for REACH, switch bid strategy, pick conversion actions). It also states when NOT to use it: 'NOT SETTABLE ANYWHERE IN THE PLATFORM' lists settings this tool cannot change, and it names sibling tools for related operations (list_linkedin_conversions, search_campaigns_by_names, check_campaign_launch_readiness). This is exemplary routing guidance.

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