Gumlet MCP

update_image_source

Update settings on an image source that already exists. This does not create a source or purge cached images.

Input Schema

Name	Required	Description
`aws`	No	This is a required field if source type is aws.
`gcs`	No	This is a required field if source type is gcs.
`type`	No
`azure`	No	This is a required field if source type is azure.
`cname`	No	List of verified CNAMEs
`proxy`	No	This is a required field if source type is proxy.
`linode`	No	This is a required field if source type is linode.
`wasabi`	No	This is a required field if source type is wasabi.
`backblaze`	No	This is a required field if source type is backblaze.
`dostorage`	No	This is a required field if source type is dostorage.
`is_active`	No	Enable / disable source.
`webfolder`	No	This is a required field if source type is webfolder.
`cloudflare`	No	This is a required field if source type is cloudflare.
`cloudinary`	No	This is a required field if source type is cloudinary.
`temp_cname`	No
`error_image`	No	URL for error image to display when we get broken image from your origin.
`secure_urls`	No	Whether the URL signing is enabled
`cdn_cache_time`	No	CDN cache time in seconds.
`default_params`	No
`image_source_id`	Yes	image source id which you want to update
`request_headers`	No
`fallback_origins`	No	List of fallback origins
`response_headers`	No
`browser_cache_time`	No	Browser cache time in seconds. For example setting this to 3600 caches the image in browser for 3600 seconds (1 hour)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 15, 2026

addedInput schema / properties / fallback_origins / items / properties / conditions / items / properties

Added value: +{
+  "function": {
+    "type": "string"
+  },
+  "value": {
+    "type": "string"
+  }
+}

addedInput schema / properties / fallback_origins / items / properties / conditions / items / required
```
Added value: +[
+  "function",
+  "value"
+]
```
changedInput schema / properties / fallback_origins / items / properties / conditions / items / type
```
Previous value: -"string"New value: +"object"
```
addedInput schema / properties / fallback_origins / items / properties / conditions / items / x-apidog-orders
```
Added value: +[
+  "function",
+  "value"
+]
```

changedInput schema / properties / fallback_origins / items / required

Previous value: -[
-  "conditions",
-  "name",
-  "type",
-  "replace_operation"
-]New value: +[
+  "name",
+  "type"
+]

addedInput schema / properties / secure_urls

Added value: +{
+  "description": "Whether the URL signing is enabled",
+  "type": "boolean"
+}

changedInput schema / properties / type / enum

Previous value: -[
-  "proxy",
-  "direct-upload",
-  "webfolder",
-  "aws",
-  "gcs",
-  "dostorage",
-  "wasabi",
-  "cloudinary",
-  "azure",
-  "linode",
-  "backblaze",
-  "cloudflare"
-]New value: +[
+  "proxy",
+  "direct-upload",
+  "webfolder",
+  "aws",
+  "gcs",
+  "dostorage",
+  "wasabi",
+  "cloudinary",
+  "azure",
+  "linode",
+  "backblaze",
+  "cloudflare",
+  "imgix",
+  "wordpress",
+  "hetzner"
+]

addedInput schema / properties / type / x-apidog-enum

Added value: +[
+  {
+    "description": "",
+    "name": "",
+    "value": "proxy"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "direct-upload"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "webfolder"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "aws"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "gcs"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "dostorage"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "wasabi"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "cloudinary"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "azure"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "linode"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "backblaze"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "cloudflare"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "imgix"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "wordpress"
+  },
+  {
+    "description": "",
+    "name": "",
+    "value": "hetzner"
+  }
+]

First observedOct 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=false and readOnlyHint=false, so the safety profile is partially covered. The description usefully confirms that cached images are not purged and no source is created, but it omits critical behavior for a 24-param update: whether the call is a partial patch or a full replace, and what auth is required.

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

Conciseness5/5

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

Two short sentences, front-loaded with the core action and immediately followed by the boundary conditions. No filler; every clause earns its place.

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?

An output schema exists, so return values need not be explained. However, for a mutation tool with 24 parameters and no idempotency guarantee (idempotentHint=false), the description should clarify partial-vs-full update semantics and the consequence of omitting nested provider blocks; that gap leaves it only minimally 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 79%, so the schema already documents most fields (type enums, per-provider required blocks, cache-time semantics). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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+resource ('Update settings on an image source that already exists') and the negation 'does not create a source or purge cached images' draws a clear boundary against create_image_source and purge_image_cache/image_purge. It stops short of naming those siblings explicitly, so an agent must infer the routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The exclusion clause ('does not create... or purge cached images') gives a when-not signal, but there is no positive when-to-use guidance, no prerequisites, and no named alternative for the excluded cases. Usage is only implied.

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?