Skip to main content
Glama

Iminify

by com.iminify
OverviewDiscussionsAdmin

Rename an image

rename_image
Idempotent

Change the name a finished image's optimized copy downloads under, for example to an SEO-friendly name like "red-running-shoes". The extension is always the delivered format's, so a typed one is dropped. The original keeps the name it was sent with.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe image's id.
nameYesThe new name, without an extension.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe image's id.
hintNoWhat to do next, when the status alone does not say.
nameNoThe name the optimized copy downloads under.
statusNo
scan_idNoThe page scan that found it, if one did.
originalNo
settingsNo
optimizedNoNull until the image has finished.
share_urlNoIts public page, once shared.
created_atNo
updated_atNo
saved_bytesNoNegative when the optimized copy is larger.
saved_percentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "created_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hint": {
+      "description": "What to do next, when the status alone does not say.",
+      "type": "string"
+    },
+    "id": {
+      "description": "The image's id.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The name the optimized copy downloads under.",
+      "type": "string"
+    },
+    "optimized": {
+      "description": "Null until the image has finished.",
+      "properties": {
+        "download_url": {
+          "description": "Works without a token for an hour.",
+          "type": "string"
+        },
+        "format": {
+          "type": "string"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "name": {
+          "type": "string"
+        },
+        "size": {
+          "description": "Bytes.",
+          "type": "integer"
+        },
+        "width": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "name",
+        "format",
+        "size",
+        "width",
+        "height",
+        "download_url"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "original": {
+      "properties": {
+        "download_url": {
+          "description": "Works without a token for an hour.",
+          "type": "string"
+        },
+        "format": {
+          "type": "string"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "name": {
+          "type": "string"
+        },
+        "size": {
+          "description": "Bytes.",
+          "type": "integer"
+        },
+        "width": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "name",
+        "format",
+        "size",
+        "width",
+        "height",
+        "download_url"
+      ],
+      "type": "object"
+    },
+    "saved_bytes": {
+      "description": "Negative when the optimized copy is larger.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "saved_percent": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "scan_id": {
+      "description": "The page scan that found it, if one did.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "settings": {
+      "properties": {
+        "height": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "keep_metadata": {
+          "type": "boolean"
+        },
+        "level": {
+          "enum": [
+            "none",
+            "lossless",
+            "ultra",
+            "smart",
+            null
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "scale": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "width": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "level",
+        "keep_metadata",
+        "width",
+        "height",
+        "scale"
+      ],
+      "type": "object"
+    },
+    "share_url": {
+      "description": "Its public page, once shared.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "enum": [
+        "queued",
+        "optimizing",
+        "completed",
+        "failed",
+        "already-optimized",
+        "cancelled"
+      ],
+      "type": "string"
+    },
+    "updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses crucial behaviors: the extension always follows the delivered format, a typed extension is dropped, and the original file keeps its original name. This adds real operational insight that the annotations alone do not provide.

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?

Three sentences carry all the essential information with no filler. The main action is stated first, followed by the two key behavioral caveats, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description, combined with complete schema documentation and annotations, covers everything an agent needs to call this tool correctly. Output schema is present, so return values need no explanation, and the behavioral notes address the main edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds semantic nuance by explaining the extension behavior and giving a concrete example of an acceptable name, which clarifies the 'name' parameter beyond the schema's brief description.

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

Purpose5/5

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

The description states a specific verb and resource: it changes the download name of a finished image's optimized copy. It even gives a concrete example and distinguishes itself from any tool that would rename the original file, making its scope unmistakable.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: after an image is finished, to set an SEO-friendly download name. It does not explicitly name alternative tools, but the sibling list contains no competing rename tool, and the note that the original is untouched implicitly tells agents this is not for renaming source files.

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

All Iminify 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