Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_file_media_source

Create and save a UFileMediaSource asset in Unreal Engine that points to a movie file path and is registered in project content; existing assets stay unchanged.

Instructions

Create a UFileMediaSource asset at package_path/name that points at a movie file path, register it and save it; the file does not need to exist. An existing asset is returned unchanged (file_path is not applied). Returns asset_path, the stored file_path, created and saved.

Returns: { media_source_name, asset_path, created, already_exists, file_path, saved, save_error }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the file media source asset to create.
file_pathYesMovie file on disk, absolute or "./"-relative to the project Content folder, e.g. "./Movies/Intro.mp4"; a path inside Content is stored in that relative form.
package_pathNoTarget content package path where the asset is created (default /Game/Media)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / file_path / description
      Previous value: -"The movie file path the source references (e.g."New value: +"Movie file on disk, absolute or \"./\"-relative to the project Content folder, e.g. \"./Movies/Intro.mp4\"; a path inside Content is stored in that relative form."
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-readonly/non-destructive. The description adds real behavior beyond them: the target file 'does not need to exist' and an existing asset 'is returned unchanged (file_path is not applied)', plus the save_error field. This is exactly the extra context that matters for a create-and-save tool.

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 front-loaded sentences carry the behavior, but there is minor redundancy: 'Returns asset_path, the stored file_path, created and saved' is largely re-stated by the explicit return-object line that follows. Otherwise lean.

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?

No output schema exists, so the description compensates by enumerating the returned fields and the save_error path. Combined with the existing-asset and file-need-not-exist behavior, an agent has enough to call it correctly.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning: it explains that package_path and name compose the target ('at package_path/name') and that file_path may reference a nonexistent file, going beyond the schema's own wording.

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?

States a specific verb and resource ('Create a UFileMediaSource asset') and pins the scope with 'at package_path/name that points at a movie file path'. This distinguishes it from siblings like create_media_player and create_media_texture without needing to open either schema.

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 conveys what triggers this tool (pointing at a movie file to make a media source) but never states when to use it versus alternatives, nor prerequisites. Usage is implied rather than spelled out, which fits a 3.

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

Deploy Server

Other Tools