Metadata MCP Connector

Create or Update LinkedIn CTV (Connected TV) Ad

create_update_ctv_ad

Destructive

Create OR update a LinkedIn CTV (Connected TV) video ad. LinkedIn only. TO UPDATE: include id; to CREATE: omit it.

                            CTV ads play on streaming TV inventory through the LinkedIn Audience
                            Network. On the platform they are LinkedIn VIDEO ads with adType=CTV,
                            and they carry rules the campaign must meet:
                              - Campaign type Brand Awareness only (never Lead Gen); the LinkedIn
                                channel launches as objective BRAND_AWARENESS optimized for REACH.
                              - The LinkedIn channel MUST use AUTO_BID (a manual bid fails
                                pre-launch validation); `update_linkedin_channel_settings` sets it.
                              - Audiences and target groups may target the United States and
                                Canada ONLY; any other location fails pre-launch validation.
                              - Video spec, enforced when the creative is uploaded: 6 to 60 seconds,
                                1920x1080 or 1280x720, at most 500 MB. LinkedIn recommends exactly
                                15, 30, 45 or 60 seconds for delivery.

                            CREATIVE WORKFLOW:
                              1. Upload the video via `upload_video_creative` with `usage_type: "CTV"`
                                 -> response gives `id` (the videoLibraryId). The platform runs the
                                 CTV checks at that step and rejects a non-compliant file.
                              2. Pass that integer as `creativeID` here. A video uploaded without
                                 the CTV usage type is not eligible for a CTV ad.
                              3. Ann attaches the returned ad id to a Brand Awareness campaign's
                                 LinkedIn channel like any other ad.

                            ALSO KNOWN AS: connected tv ad, ctv ad, streaming tv ad, linkedin tv ad,
                            ott ad, tv commercial on linkedin.

                            KEYWORDS: ctv, connected tv, streaming, tv, ott, linkedin ctv, video,
                            brand awareness, reach, audience network, commercial.

                            CLIENT-SIDE VALIDATION (refuses what the platform UI would also reject):
                              - adName: required, max 50 chars, same pattern as the other ad tools.
                              - creativeID: required integer (videoLibraryId).
                              - linkedinDisplayURL: required, ABSOLUTE (http:// or https://), max 2000.
                              - linkedinHeadline: required, max 200. linkedinCTA: required enum.
                              - linkedinText: optional, max 3000. No description field (same DTO as
                                LinkedIn VIDEO ads).

                            COMMON CTA VALUES: same as `create_update_video_ad` on LinkedIn.

                            RESPONSE: same envelope as `create_update_video_ad` (`created_ads[]` with
                            adType "CTV", channelType "LINKEDIN").

                            See `create_update_video_ad` for in-feed video ads and
                            `create_update_image_ad` for image / GIF ads.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ads_data`	Yes	Array of LinkedIn CTV ads to create or update.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=true, and the description thoroughly complements them by detailing mutation behavior, client-side validation, the requirement for AUTO_BID, location restrictions, video specs, and the response envelope. It also notes that the platform runs CTV checks during upload and rejects non-compliant files, providing essential behavioral context.

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 well-structured with clear sections (purpose, constraints, workflow, validation, response). It front-loads the core purpose and then adds necessary detail. While verbose, every sentence contributes value given the tool's complexity; no fluff is present.

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?

The description is exceptionally complete: it covers the campaign prerequisites, bid strategy, location limits, video specifications, the two-step workflow, client-side validation, CTA enums, response format, and cross-references to sibling tools. Nothing an agent needs to correctly invoke this tool is missing, even including keywords and synonyms.

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 coverage is 100% and the schema already documents each field, but the description adds significant meaning: it explains that creativeID is the videoLibraryId from upload_video_creative with usage_type CTV, clarifies that id must be included for updates, and notes the absence of a description field (same DTO as video ads). It also lists client-side validation rules that map to parameters, going beyond schema text.

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 explicitly states the tool creates or updates a LinkedIn CTV video ad, naming the specific resource and action. It also distinguishes itself from sibling tools like create_update_video_ad and create_update_image_ad by clarifying which ad type it handles, making it impossible to confuse.

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 provides explicit when-to-use guidance: it names alternatives (create_update_video_ad for in-feed video ads, create_update_image_ad for image/GIF ads) and clearly outlines the workflow involving upload_video_creative and update_linkedin_channel_settings. It also lists hard constraints (Brand Awareness campaign, AUTO_BID, US/Canada only) that determine correct usage.

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 tools Inspect

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

Need Help?