Gumlet MCP

update_profile

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

Input Schema

Name	Required	Description	Default
`vc`	No	Video Codecs
`pad`	No	This transformation can be used to add padding to the video.
`crop`	No	This transformation can be used to crop the video by defining a rectangular area within the dimensions of the output video.
`name`	No	Profile name or identifier.
`trim`	No	Trim transformation can be used to trim videos based on time duration.
`width`	No	Resize 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`.
`format`	No	Transcode and deliver the asset in the requested format. The options can be one of `ABR` (HLS + DASH) and `MP4`.	ABR
`height`	No	Resize 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_only`	No	This 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_drm`	No	Enable DRM encryption for transcoded videos. Gumlet supports Widevine and FairPlay DRMs.
`mp4_access`	No	Creates `mp4` version for download purpose in case of `MPEG-DASH` or `HLS` delivery format. Default: `false`
`profile_id`	No	Profile id of the profile which needs to be deleted.
`resolution`	No	Resize 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`.
`transcribe`	No	To generate the subtitles in the native audio.
`animated_gif`	No	Create an animated GIF from a video.
`text_overlay`	No	Text overlay can be used to brand a video or add a label in the form of text.
`image_overlay`	No	Image overlay can be used to brand a video or add a visual label in the form of an image.
`profile_id__path`	Yes	Profile id of the profile which need to be updated. (Path parameter)
`generate_chapters`	No	Whether Gumlet should generate chapters.
`generate_subtitles`	No	Gumlet 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_encoding`	No	Gumlet 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_description`	No	Whether Gumlet should generate descriptions.
`process_low_resolution_input`	No	Currently, 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

removedInput schema / properties / generate_subtitles / properties / transcribe

Removed value: -{
-  "default": true,
-  "description": "This is by default true to generate the subtitles in the native audio.",
-  "type": "boolean"
-}

addedInput schema / properties / transcribe

Added value: +{
+  "default": false,
+  "description": "To generate the subtitles in the native audio.",
+  "type": "boolean"
+}

First observedOct 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false. The description adds genuinely useful behavior: it is a partial update where omitted fields are preserved, which matters for a 23-parameter mutation. It says nothing about permissions, whether nested objects are replaced wholesale vs merged, or the odd duplication of profile_id in both path and body.

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, front-loaded with the action. The second sentence is slightly awkward and repeats 'in the existing profile', but there is no filler or bloat.

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?

Output schema and annotations cover return values and safety, and the partial-update note covers the main mutation risk. But for a 23-parameter nested-object tool the description is thin — it omits merge semantics for nested objects (pad/crop/trim/overlays), the MP4-only constraints on width/height, and the path-vs-body profile id question.

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 coverage is 100% across 23 properties, so the schema carries the parameter burden and the description adds nothing per-field. Worse, the schema lists both profile_id__path (required) and a profile_id body param described as 'the profile which needs to be deleted' — the description does not clarify this ambiguity.

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 that only supplied settings are changed. It does not distinguish itself from siblings such as create_profile, delete_profile, or get_profile, and never explains what a 'profile' is in this product (a transcode profile).

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 statement of when to use this versus create_profile/delete_profile/get_profile, and no prerequisites. The only usable signal is implicit in 'only updated in the existing profile', which implies partial-update semantics but is phrased as a behavior, not as a usage rule.

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

All Gumlet MCP tools Inspect

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

Need Help?