Skip to main content
Glama

Metadata MCP Connector

Upload Video Creative

upload_video_creative

Upload videos directly to the Metadata platform library to create video creatives. Downloads videos from provided URLs and uploads them to the platform.

            WARNING: VIDEO-ONLY: The downloaded file MUST have a `video/*` content-type
            (e.g. video/mp4, video/quicktime). GIFs and image formats are
            rejected — use `upload_image_creative` for those.

            WARNING: WHEN YOU NEED TO CALL THIS:
            Call this BEFORE `create_update_video_ad` ONLY when you don't already
            have a videoLibraryId. If the user (or an earlier step) has
            already given you a creativeID for the video, skip the upload
            and pass that id straight to `create_update_video_ad`.

            WORKFLOW INTEGRATION (when an upload IS needed):
            1. Upload your video URL with this tool → response contains the integer `id` (the videoLibraryId).
            2. Pass that integer `id` as `creativeID` in `create_update_video_ad`.

            COMMON WORKFLOWS:
            - Upload existing video → Get videoLibraryId → Use as creativeID in `create_update_video_ad`.
            - For Reddit VIDEO ads, ALSO upload a thumbnail image via `upload_image_creative` and pass that image
              library id as `redditThumbnailLibraryId` to `create_update_video_ad`.

            REQUIRED PARAMETERS:
            - videos: Array of video URLs to upload.

            OPTIONAL PARAMETERS:
            - thumbnail_library_id: Existing imageLibraryId to attach to the
              uploaded video as its platform thumbnail. Most callers don't
              need this — Reddit VIDEO ads handle thumbnails at ad-creation
              time via `redditThumbnailLibraryId`, not here.
            - usage_type: "CTV" to upload the video for a LinkedIn CTV
              (Connected TV) ad. The platform then validates the file as CTV
              inventory (6 to 60 seconds, 1920x1080 or 1280x720, at most
              500 MB; LinkedIn recommends exactly 15, 30, 45 or 60 seconds)
              and only such an upload can back `create_update_ctv_ad`. A
              non-compliant file is rejected at upload with the platform's
              reason. Omit for in-feed video ads.

            VIDEO REQUIREMENTS:
            - URLs must be valid and publicly accessible.
            - Supported formats: MP4 (recommended), MOV, and other video/* MIME types.
            - For GIFs (image/gif): use `upload_image_creative` instead.

            RESPONSE FORMAT:
            Returns array of objects, one per video. `id` is returned as a
            string (the platform's library ids are integers but the upload
            response stringifies them); pass it to `create_update_video_ad` as an
            integer (Python `int(id)` if you need the cast).
            [
                {
                    "url": "https://example.com/video.mp4",
                    "name": "video.mp4",
                    "id": "12345",                # videoLibraryId — use as creativeID in create_update_video_ad
                    "success": true
                },
                {
                    "url": "https://example.com/bad.mp4",
                    "name": "bad.mp4",
                    "id": null,
                    "success": false,
                    "error": "Download failed: Connection timeout"
                }
            ]

            ERROR HANDLING:
            - If one upload fails, others continue.
            - Each result includes a success flag and (on failure) an error message.
            - A content-type that does not start with `video/` is rejected
              with a clear error pointing the caller at `upload_image_creative`.
            

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videosYesArray of video URLs to upload to the platform library.
usage_typeNoSet to CTV when the video is for a LinkedIn Connected TV ad; the platform validates the CTV spec at upload. Omit for in-feed video ads.
thumbnail_library_idNoOptional existing imageLibraryId to attach as the video's platform thumbnail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds substantial behavioral detail: it downloads from URLs, validates content-type, returns a per-video array with success flags and error messages, and handles partial failures. It also discloses response type casting (id as string). This far exceeds what annotations convey.

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?

The description is long but every section earns its place: warnings, workflow steps, common workflows, parameter explanations, response format, and error handling. It is front-loaded with the most critical warning (video-only) and the when-to-call rule. The use of headings and numbered lists keeps it scannable despite length.

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?

With no output schema, the description provides a full response format example, including failure cases. It covers workflow integration with create_update_video_ad, prerequisites (public URLs, video/* MIME types), and error handling (partial success). Nothing an agent needs to call 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?

Although schema coverage is 100%, the description enriches each parameter: usage_type gets CTV-specific validation details (duration, resolution, size) and its role in create_update_ctv_ad; thumbnail_library_id is clarified with when it is needed versus when Reddit handles thumbnails. It adds actionable semantics beyond the schema's terse 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: 'Upload videos directly to the Metadata platform library to create video creatives.' It clearly distinguishes from upload_image_creative by stating that GIFs and image formats are rejected and pointing to the sibling tool. This makes the purpose unmistakable.

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?

Provides explicit when-to-use guidance: 'Call this BEFORE create_update_video_ad ONLY when you don't already have a videoLibraryId,' and instructs to skip upload if a creativeID is already available. It also names the alternative (upload_image_creative) for non-video content. These are concrete decision rules, not vague hints.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources