BlitzReels Video Editor

Import Media From URL

media_import_url

Import a video, audio, or image from a user-provided direct URL into the private BlitzReels media library.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	URL of the media file to download and upload
`name`	No	Optional name for the file
`projectId`	No	Optional project ID to associate the upload with. UUID string.
`workspaceId`	No	Optional workspace ID when projectId is not provided. Defaults to the user's default workspace. UUID string.
`contentHashSha256`	No	Optional SHA-256 hex hash of file bytes for dedupe optimization. 64-character hex string.
`confirmRightsToMedia`	No	Set true only after the user confirms they own the media or have permission to import it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`media`	Yes

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate this is a mutating, non-idempotent operation, and the description's 'Import' wording is consistent with that. It adds helpful context about the destination and accepted media types, but it does not disclose behavioral nuances like network download behavior, validation failures, dedupe-by-hash semantics, or the rights confirmation requirement.

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, efficiently structured sentence that front-loads the action, resource type, source, and destination. There is no filler, and every phrase contributes to the agent's understanding.

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?

With rich schema descriptions, clear annotations, and an output schema present, the description provides enough context for an agent to call the tool correctly. It could be more complete by giving explicit routing guidance versus upload/inspect siblings, but that gap does not block correct invocation.

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?

The input schema provides 100% coverage for all six parameters, so the description does not need to restate parameter details. The description adds no new parameter-level semantics beyond the schema, but the baseline of 3 applies because the structured schema already carries that burden.

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 identifies a specific verb ('Import'), a clear resource (video, audio, or image from a direct URL), and a destination ('private BlitzReels media library'). This distinguishes it from sibling tools such as media_upload_file and media_import_inspect without requiring an agent to inspect schemas.

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 phrase 'user-provided direct URL' implies the intended use case: importing remote media into the library. However, the description never explicitly names alternatives or states when not to use this tool, such as for local file uploads or pre-import URL inspection, so usage 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.

All BlitzReels Video Editor tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation3/5

Most tools use clear domain prefixes, but several boundaries are fuzzy: clips_get and clips_manage both expose clip/export status, and update_timeline_clip overlaps with timeline_edit_apply for trim/duration changes. Detailed descriptions mitigate this, but an agent could still select the wrong tool for clip inspection or timeline edits.

Naming Consistency3/5

All names are snake_case and mostly readable, but the server mixes verb-first names (add_text_overlay, delete_timeline_items, update_timeline_clip) with noun-first domain-action names (clips_create, generation_*_create, media_import_*). The domain-prefix pattern dominates, yet the inconsistent verb placement makes the convention only partially predictable.

Tool Count1/5

58 tools is far beyond the 25+ threshold and matches the rubric's 50+ extreme-mismatch example. Even though the domain is broad, this surface would be easier for an agent to navigate if split into focused servers for media, generation, timeline editing, clips, and workflows.

Completeness3/5

Core video-editing flows are well represented: project creation/inspection, timeline item editing/deletion, media import/upload, AI generation, exports, and clips. However, lifecycle gaps remain—no project update/delete, no media asset deletion, no delete for characters or story kits, and no export cancellation—so some user requests will dead-end.

Resources

Need Help?