Skip to main content
Glama

create_asset

An asset refers to media content/video that is processed, stored, and delivered through Gumlet. This endpoint creates an asset allowing users to ingest media content into the Gumlet system for processing and delivery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
padNoThis transformation can be used to add padding to the video.
tagNoSpecify a text string or identifier which can identify an asset or bunch of assets later.
cropNoThis transformation can be used to crop the video by defining a rectangular area within the dimensions of the output video.
trimNoTrim transformation can be used to trim videos based on time duration.
inputNoURL or web address of a file that Gumlet should download to create a new asset.
titleNoSpecify a text string or identifier which can be used for filtering or searching the asset.
widthNoResize video with the given width. Can be an absolute value in pixels or a percentage value with the `%` suffix. Specified values greater than the original asset width will be ignored. Applicable only when specified format is `MP4`.
folderNoAdd this asset to an existing folder by `folder_id`.
formatNoTranscode and deliver the asset in the requested format. The options can be one of `ABR` (HLS + DASH) and `MP4`.
heightNoResize video with the given height. Can be an absolute value in pixels or a percentage value with the `%` suffix. Specified values greater than the original asset height will be ignored. Applicable only when specified format is `MP4`.
metadataNoAdd your metadata you want to associate with this asset.<br/> Example: <br/> <code> { "internal_video_id" : "123Abc" } </code>
audio_onlyNoThis flag allows Gumlet to transcode and deliver audio-only in the specified format. In this case, video transformation and thumbnails/animated GIFs would not be created. **Default: `false`**
enable_drmNoEnable DRM encryption for transcoded videos. Gumlet supports Widevine and FairPlay DRMs.
mp4_accessNoCreates `MP4` version for download purpose in case of `MPEG-DASH` or `HLS` delivery format. **Default: `false`**
profile_idNoProvide `profile_id` of the previously created video profile. This parameter will override all the parameters (except `input` and `workspace_id`) from the video profile.
resolutionNoRequired resolutions of the transformed asset in case of HLS or MPEG-DASH delivery format. Can be a comma-separated string out of the following values: `240p`, `360p`, `480p`, `540p`, `720p`, and `1080p`. Resized rendition will retain the input aspect ratio.
descriptionNoAttach some textual data with the asset. This field is neither searchable nor filterable.
playlist_idNoAdd this asset to a playlist.
animated_gifNoCreate an animated GIF from the video.
text_overlayNoText overlay can be used to brand a video or add a label in the form of text.
workspace_idNoGumlet video workspace id.
image_overlayNoImage overlay can be used to brand a video or add a visual label in the form of an image.
call_to_actionsNoA CTA is an explicit prompt within the video content encouraging viewers to take a particular action.
additional_tracksNoAdd additional Audio / Subtitle tracks to Gumlet for transcoding and delivery along with video asset track.
generate_subtitlesNoGumlet allows you to generate subtitles from the audio stream (use <a href='https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes'> ISO 639-1 </a> Language Codes)
per_title_encodingNoGumlet analyzes each input video on a wide range of visual aspects. Based on the analysis, it chooses a unique set of transcoding options for processing the video. This ensures that the output video is of optimal size and best quality. **Default: `true`**
process_low_resolution_inputNoCurrently, the minimum supported frame size is `57600` (`240x240`) pixels for `HLS/DASH` and `21025` (`145x145`) pixels for `MP4` format. However, enabling this flag will allow Gumlet to simply put your video asset into the specified delivery format without transcoding and optimization. Enabling this flag will cause any kind of specified video transformation to be ignored if you input video asset frame size is lower than the minimum supported frame size for the specified format. **Default: `false`**

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile_id / description
      Previous value: -"Provide `profile_id` of the previously created video profile. This parameter will override all the parameters (except `input` and `collection_id`) from the video profile."New value: +"Provide `profile_id` of the previously created video profile. This parameter will override all the parameters (except `input` and `workspace_id`) from the video profile."
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive write operation. The description adds only that the asset is ingested for processing and delivery; it does not disclose asynchronous processing behavior, whether an input URL is effectively required despite the empty required list, or any auth/scoping requirements.

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?

The description is two sentences and free of padding, but it leads with a definition of 'asset' rather than the action, which slightly delays the operative information. It is appropriately sized for a short summary.

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?

For a tool with 27 parameters, nested transformation objects, and multiple sibling creation paths, two sentences are not enough. The output schema covers return values, but the description does not explain the central input URL requirement, the role of workspace_id, or how this differs from direct-upload and live-asset creation.

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%, so the schema already documents all 27 parameters in detail. The description adds no parameter-level meaning beyond the schema baseline, which is acceptable under the high-coverage rule but not additive.

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 states a specific verb and resource: 'This endpoint creates an asset' and defines an asset as media content/video processed and delivered through Gumlet. It does not differentiate from sibling creation tools such as create_asset_direct_upload, create_live_asset, or import_from_vimeo, but the core purpose is clear.

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?

There is no guidance on when to use this tool versus alternatives like create_asset_direct_upload or import_from_vimeo. It also omits prerequisites such as needing an input URL or workspace context, leaving usage entirely implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources