Gumlet MCP

create_workspace

Video workspaces are top-level entities in Gumlet. You can use them to organize videos for different teams/departments or use cases.

Input Schema

Name	Required	Description	Default
`aws`	No	This is a required field if workspace type is aws.
`gcs`	No	This is a required field if workspace type is gcs.
`name`	No	Specify a text string or identifier for the workspace.
`type`	No	Video workspaces are top-level entities in Gumlet. You can use them to organize videos for different teams/departments or use cases.	direct-upload
`zoom`	No	This is a required field if workspace type is zoom.
`azure`	No	This is a required field if workspace type is azure.
`proxy`	No	This is a required field if workspace type is proxy.
`linode`	No	This is a required field if workspace type is linode.
`wasabi`	No	This is a required field if workspace type is wasabi.
`backblaze`	No	This is a required field if workspace type is backblaze.
`dostorage`	No	This is a required field if workspace type is dostorage.
`cloudflare`	No	This is a required field if workspace type is cloudflare.
`cloudinary`	No	This is a required field if workspace type is cloudinary.
`video_protection`	No	Gumlet provides multiple options for securing your video playback.
`data_localization`	No	Data localization region	us
`default_profile_id`	No	Gumlet provides the functionality of creating multiple video assets using the same set of parameters.
`insight_property_id`	No	The five to ten character unique identifier of the Gumlet Insight Property available on the dashboard.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 26, 2026

addedInput schema / properties / aws / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "bucket_region",
+  "access_key",
+  "secret",
+  "base_path",
+  "endpoint"
+]

addedInput schema / properties / azure / x-apidog-orders

Added value: +[
+  "azure_account_name",
+  "azure_container_name",
+  "azure_shared_token",
+  "azure_path"
+]

addedInput schema / properties / backblaze / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "bucket_region",
+  "endpoint",
+  "access_key",
+  "secret",
+  "base_path"
+]

addedInput schema / properties / cloudflare / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "access_key",
+  "account_id",
+  "secret",
+  "base_path"
+]

addedInput schema / properties / cloudinary / x-apidog-orders
```
Added value: +[
+  "host_name",
+  "cloud_name"
+]
```

addedInput schema / properties / data_localization

Added value: +{
+  "default": "us",
+  "description": "Data localization region",
+  "enum": [
+    "us",
+    "in",
+    "eu"
+  ],
+  "type": "string",
+  "x-apidog-enum": [
+    {
+      "description": "",
+      "name": "USA",
+      "value": "us"
+    },
+    {
+      "description": "",
+      "name": "India",
+      "value": "in"
+    },
+    {
+      "description": "",
+      "name": "Europe",
+      "value": "eu"
+    }
+  ]
+}

addedInput schema / properties / dostorage / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "bucket_region",
+  "access_key",
+  "secret",
+  "base_path"
+]

addedInput schema / properties / gcs / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "service_account_key"
+]

addedInput schema / properties / linode / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "bucket_region",
+  "access_key",
+  "secret"
+]

addedInput schema / properties / proxy / x-apidog-orders
```
Added value: +[
+  "whitelisted_domains"
+]
```

addedInput schema / properties / video_protection / x-apidog-orders

Added value: +[
+  "signed_url",
+  "signed_url_secret",
+  "blacklisted_countries",
+  "whitelisted_referrers"
+]

addedInput schema / properties / wasabi / x-apidog-orders

Added value: +[
+  "bucket_name",
+  "bucket_region",
+  "access_key",
+  "secret",
+  "base_path"
+]

addedInput schema / properties / zoom / x-apidog-orders
```
Added value: +[
+  "secret"
+]
```

First observedOct 7, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds no behavioral context beyond the generic workspace concept—nothing about permissions, storage-type side effects, or what happens when configuration is incomplete. It does not contradict the annotations, but it adds little.

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?

The description is short and wastes little space, but it is not front-loaded around the actual action of creating a workspace. Its two sentences describe workspace semantics rather than the operation the tool performs.

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 mutation tool with 17 parameters, many conditional storage-type objects, no required top-level parameters, and an output schema, the description is too thin. It omits the creation action, storage-type selection logic, and any guidance on required fields for each workspace type, even though the schema captures those details.

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 itself documents the many nested storage objects, enum values, and type-conditional fields. The description adds no parameter-specific meaning; its only relevant sentence duplicates the schema's type description. With full schema coverage, the baseline of 3 is appropriate.

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

Purpose2/5

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

The description explains what a video workspace is conceptualized as, but never states that this tool creates one. It does not distinguish create_workspace from siblings like get_workspace, list_workspaces, update_workspace, or delete_workspace, leaving the agent to infer the action from the tool name alone.

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?

It mentions that workspaces organize videos for teams or use cases, but gives no guidance on when to call create_workspace versus alternatives. There are no prerequisites, exclusions, or sibling references.

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?