Skip to main content
Glama

Gumlet MCP

by com.gumlet.mcp
OverviewDiscussionsAdmin

update_profile

Update an existing profile. Settings provided in body parameters will only be updated in the existing profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vcNoVideo Codecs
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.
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`**
profile_idNoProfile id of the profile which needs to be deleted.
resolutionNoResize 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`.
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.
profile_id__pathYesProfile id of the profile which need to be updated. (Path parameter)
generate_chaptersNoWhether Gumlet should generate chapters.
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). You can remove this object if you don't 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`**
generate_descriptionNoWhether Gumlet should generate descriptions.
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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare this is a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description usefully adds that only supplied body parameters are changed, which is meaningful patch semantics beyond the annotations, but it omits auth requirements, whether edits affect in-flight transcodes, and reversibility.

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 short sentences with the operation stated first and the merge behavior second; no filler. Slightly redundant phrasing ('updated in the existing profile') but appropriately sized for the core claim.

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?

For a 22-parameter, nested-object mutation with an output schema present, the description covers the essential patch semantics but says nothing about the profile domain (transcoding/DRM/overlays), validation failure modes, or how updates interact with existing assets. Adequate minimum, not complete.

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% across all 22 parameters including nested transformation objects, so the schema carries the full parameter burden. The description adds no per-parameter detail, which is acceptable at this coverage level but is the baseline rather than a value-add.

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?

States a specific verb and resource ('Update an existing profile') and clarifies the merge/patch scope of the operation. It does not differentiate itself from siblings like create_profile, get_profile, or delete_profile, leaving the agent to infer the read/write boundary.

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 guidance on when to use this versus create_profile (new profile) or get_profile (inspect one), and no prerequisites such as required permissions or whether the profile must be unassigned to assets. Only the implicit patch semantics hint at usage.

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