Skip to main content
Glama

Gumlet MCP

by com.gumlet.mcp
OverviewDiscussionsAdmin

create_profile

Gumlet provides the functionality of creating multiple video assets using the same set of parameters. A Video profile is a set of parameters that can be referenced/used while creating a video as a single parameter.

Input Schema

NameRequiredDescriptionDefault
padNoThis transformation can be used to add padding to the video.
cropNoThis transformation can be used to crop the video by defining a rectangular area within the dimensions of the output video.
nameNoProfile name or identifier.Gumlet-Profile-1
trimNoTrim transformation can be used to trim videos based on time duration.
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. Only applicable when specified `format` is `MP4`.
formatNoTranscode and deliver the asset in the requested format. The options can be one of `ABR` (HLS + DASH) and `MP4`.ABR
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. Only applicable when specified `format` is `MP4`.
audio_onlyNoThis flag allows Gumlet to transcode and deliver audio-only in the specified format. In this case,This 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`**
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.
transcribeNoThis will generate the subtitles in the native audio.
animated_gifNoCreate an animated GIF from a video.
text_overlayNoText overlay can be used to brand a video or add a label in the form of text.
image_overlayNoImage overlay can be used to brand a video or add a visual label in the form of an image.
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). Remove this object if you do not want to generate AI subtitles.
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. Changed2 schema fields changed
    • removedInput schema / properties / generate_subtitles / properties / transcribe
      Removed value: -{
-  "default": true,
-  "description": "This will generate the subtitles in the native audio.",
-  "type": "boolean"
-}
    • addedInput schema / properties / transcribe
      Added value: +{
+  "default": false,
+  "description": "This will generate the subtitles in the native audio.",
+  "type": "boolean"
+}
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, which covers the safety profile, and the description adds conceptual context about what a profile represents. However, it does not disclose behavior the agent would care about: whether repeated calls with the same name create duplicates or error, whether a workspace scope is needed, or what validation applies to the 18 optional parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, but the second largely restates the first ('same set of parameters' / 'a set of parameters ... as a single parameter'). It is also mis-front-loaded: the leading clause is about creating video assets, not about creating a profile, so the agent reads the wrong operation first.

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 an 18-parameter creation tool, the description leaves out the essential workflow context: that the created profile id is then consumed by create_asset, and that a name defaults to 'Gumlet-Profile-1'. An output schema exists, so return values need not be explained, but the usage linkage is missing.

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% and every nested object (pad, crop, trim, text_overlay, image_overlay, animated_gif) is documented inline, so the schema carries the meaning. The description adds nothing parameter-specific, which is acceptable at this coverage level but means no bonus.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines what a video profile IS (a reusable set of parameters) but never states the action plainly: it opens with 'Gumlet provides the functionality of creating multiple video assets', which describes the benefit rather than the operation ('create a profile'). It is understandable but does not distinguish itself from siblings like create_asset, update_profile, or list_profiles.

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?

No when-to-use guidance: it never says to call this before create_asset, that the resulting profile is referenced as a single parameter, or that update_profile/delete_profile exist for lifecycle management. The lifecycle relationship is only implied by the phrase 'referenced/used while creating a video'.

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

All Gumlet MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources