Skip to main content
Glama

Upload Video

upload_video
Destructive

Uploads a local video file to BGRemover Video and returns a CDN URL for use as video_url or media_url in other BGRemover Video tools.

Instructions

This tool will upload a local video file to BGRemover Video and return a CDN URL that can be passed as video_url or media_url to another BGRemover Video tool. It takes one argument: - file_path (str, required): Absolute local path to the video file.

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": {
      "file_path": "<file_path>"
    },
    "name": "upload_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute local file path to the video to upload (e.g. '/Users/me/Downloads/clip.mp4').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, destructive, open-world, non-idempotent operation, and the description is consistent with that; it adds that the file leaves the local machine and a CDN URL comes back, which is genuinely useful context beyond the annotation flags. However, it says nothing about authentication, credit consumption (relevant given the check_credits sibling), size/format limits, or that re-uploading the same file creates a new asset rather than overwriting one.

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?

Two sentences, front-loaded with the action and outcome, then the argument. The bullet-style restatement of the single parameter is largely redundant with a fully documented schema, but nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with a complete schema and informative annotations, the description covers the essentials, including the otherwise-undocumented fact that a CDN URL is returned (important since there is no output schema). Remaining gaps — limits, credits, retry semantics — are minor rather than blocking.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already states 'Absolute local file path to the video to upload' with an example. The description only restates 'file_path (str, required): Absolute local path' without adding format, size, or validation detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('upload a local video file to BGRemover Video') and even states the return value (a CDN URL). The 'video' qualifier implicitly separates it from the upload_image sibling, but it never names that sibling or states the split explicitly, so it falls short of a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It usefully tells the agent what to do with the result — pass the CDN URL as video_url or media_url to another BGRemover Video tool — which implies the upload-then-process workflow. It does not say when *not* to use this tool (e.g. for images, or when the asset already has a URL) or point to upload_image, so guidance is only implied.

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