Skip to main content
Glama

import_video

Import a video into a project folder and correct its orientation so portrait phone clips appear upright.

Instructions

Import (copy) a video into the project source folder.

bake_orientation: when True (default), bake displaymatrix rotation so portrait phone clips are upright for all downstream tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
video_pathYes
bake_orientationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the full burden. It explains the bake_orientation behavior but omits side effects like overwrites, permissions, or error conditions.

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?

Two sentences with no wasted words; purpose is front-loaded and parameter explanation is immediately after.

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

Completeness2/5

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

Despite an output schema, the tool has 3 parameters and 0% schema coverage. The description covers only one parameter and lacks context on formats, size limits, or prerequisites, leaving many gaps.

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 coverage is 0% so the description must compensate. It explains bake_orientation in detail but leaves project_id and video_path undocumented (e.g., format, source location).

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 clearly states the verb 'import (copy)' and the resource 'a video into the project source folder', distinguishing it from sibling tools like add_graphics or process_audio.

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?

The description implies usage for copying videos but provides no explicit when-to-use or when-not-to-use guidance, nor alternatives among the many sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dhirajlochib/VidMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server