Skip to main content
Glama

move_videos

DestructiveIdempotent

Move multiple Loom videos to a different folder to organize your content by selecting video IDs and a destination folder.

Instructions

Move one or more Loom videos to a different folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idsYesList of Loom video IDs to move
folder_idYesThe destination folder ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds no additional behavioral context beyond stating the action. It does not disclose whether moves are reversible, permissions required, or effects on original location.

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 a single, concise sentence that clearly communicates the tool's function without unnecessary words. It is front-loaded and efficient.

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

Completeness3/5

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

While the core functionality is clear, the description lacks details about return values (though an output schema exists), error conditions, batch limits, or side effects. For a mutation tool with destructive hint, more completeness would be beneficial.

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?

Both parameters (video_ids, folder_id) are fully described in the input schema. The tool description does not add any additional meaning beyond what the schema already provides.

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 action ('Move one or more Loom videos to a different folder'), specifying the resource (videos) and destination (folder). It distinguishes itself from sibling tools like move_folders, which moves folders instead.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as archive_videos or delete_video. It does not mention prerequisites, limitations, or when not to use it.

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/karbassi/mcp-loom'

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