Skip to main content
Glama

Import a video by link

clipember_upload_media_from_url

Add the user's own video (not a clip) to ClipEmber from a direct https link to the video file (MP4/MOV/WebM, up to 1 GB and 15 minutes). ClipEmber downloads and checks it in the background and returns its mediaId right away with status "uploading"; poll clipember_get_media until it is "ready" (or post straight away with clipember_create_post — the post waits for the video). Use only videos the user owns or may publish. YouTube/TikTok page links are not video files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "clipember_upload_media_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirect https link to the video file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint, non-idempotent, non-destructive), the description discloses the asynchronous contract that matters most: the download and validation run in the background, the call returns a mediaId immediately with status "uploading", and the asset is not usable until "ready". Size and duration caps (1 GB / 15 minutes) further set expectations for failure.

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?

Front-loaded with what the tool does and its constraints, then the follow-up path, then the exclusion. Every sentence contributes a distinct fact; nothing is restated from the schema or annotations.

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 one-parameter import tool with no output schema, the definition covers the async return shape, the polling follow-up, the alternative immediate-post path, and the acceptance constraints. An agent could call it and handle the result correctly without further information.

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%, so the url parameter is already documented. The description still adds real meaning: the link must point at the video file itself rather than a platform page, and it enumerates the accepted containers (MP4/MOV/WebM) with size and duration bounds.

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 plus resource and immediately narrows scope: "Add the user's own video (not a clip) ... from a direct https link to the video file." It names accepted formats and limits, and the parenthetical "not a clip" distinguishes this from clip-creation flows.

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?

It gives explicit routing: after the call, poll clipember_get_media until "ready", or skip polling and call clipember_create_post because the post waits. It also states an exclusion ("YouTube/TikTok page links are not video files") and a licensing condition (only videos the user owns or may publish).

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